home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
InfoMagic Standards 1994 January
/
InfoMagic Standards - January 1994.iso
/
ccitt
/
1988
/
troff
/
8_7_13.tro
< prev
next >
Wrap
Text File
|
1991-12-22
|
145KB
|
5,639 lines
.rs
.\" Troff code generated by TPS Convert from ITU Original Files
.\" Not Copyright (~c) 1991
.\"
.\" Assumes tbl, eqn, MS macros, and lots of luck.
.TA 1c 2c 3c 4c 5c 6c 7c 8c
.ds CH
.ds CF
.EQ
delim @@
.EN
.nr LL 40.5P
.nr ll 40.5P
.nr HM 3P
.nr FM 6P
.nr PO 4P
.nr PD 9p
.po 4P
.rs
\v'|.5i'
.sp 2P
.LP
\fBRecommendation\ X.413\fR
.RT
.sp 2P
.ce 1000
\fBMESSAGE HANDLING SYSTEMS:\fR
.EF '% Fascicle\ VIII.7\ \(em\ Rec.\ X.413''
.OF '''Fascicle\ VIII.7\ \(em\ Rec.\ X.413 %'
.ce 0
.sp 1P
.ce 1000
\fBMESSAGE STORE: ABSTRACT\(hySERVICE DEFINITION\fR
.FS
Recommendation\ X.413 and ISO\ 10021\(hy5 [Information processing systems
\(em Text
Communication \(em MOTIS \(em Message Store: Abstract\(hyservice definition]
were
developed
in close collaboration and are technically aligned, except for the differences
noted in Appendix\ G.
.FE
.ce 0
.sp 1P
.ce 1000
(\fIMelbourne, 1988\fR )
.sp 9p
.RT
.ce 0
.sp 1P
.PP
The establishment in various countries of telematic services and
computer\(hybased store\(hyand\(hyforward message services in assocation
with public
data networks creates a need to produce standards to facilitate international
message exchange between subscribers to such services.
.sp 1P
.RT
.sp 2P
.LP
The\ CCITT,
.sp 1P
.RT
.sp 1P
.LP
\fIconsidering\fR
.sp 9p
.RT
.PP
(a)
the need for message handling services;
.PP
(b)
the need to transfer and store messages of different
types;
.PP
(c)
that Recommendation\ X.200 defines the reference model of
open systems interconnection of CCITT applications;
.PP
(d)
that Recommendations X.208, X.217, X.218, and X.219 provide the foundation
for CCITT applications;
.PP
(e)
that the X.500\(hyseries Recommendations specify directory
services and systems;
.PP
(f
)
that message handling services and systems are
specified in a series of Recommendations: X.400, X.402, X.403, X.407, X.408,
X.411, X.413, and X.419;
.PP
(g)
that interpersonal messaging is specified in
Recommendations\ X.420 and T.330;
.sp 1P
.LP
\fIunanimously declares\fR
.sp 9p
.RT
.PP
(1)
that the message stores abstract\(hyservice definition is
specified in Section\ 2;
.PP
(2)
that the general\(hyattribute\(hytypes and the
general\(hyauto\(hyaction\(hytypes are specified in Section\ 3;
.PP
(3)
that the procedures for message store and the ports
realization are specified in Section\ 4.
\v'1P'
.sp 1P
.ce 1000
TABLE OF CONTENTS
.ce 0
.sp 1P
.LP
SECTION\ 1\ \(em\ \fIIntroduction\fR
.sp 1P
.RT
.sp 2P
.LP
0
Introduction
.sp 1P
.RT
.sp 1P
.LP
1
Scope
.sp 9p
.RT
.sp 1P
.LP
2
References
.sp 9p
.RT
.sp 1P
.LP
3
Definitions
.sp 9p
.RT
.sp 1P
.LP
4
Abbreviations
.sp 9p
.RT
.sp 1P
.LP
5
Conventions
.bp
.sp 9p
.RT
.sp 2P
.LP
SECTION\ 2\ \(em\ \fIMessage store abstract\(hyservice definitions\fR
.sp 1P
.RT
.sp 1P
.LP
6
Message store model
.sp 9p
.RT
.sp 1P
.LP
7
Abstract\(hybind and abstract\(hyunbind\(hyoperations
.sp 9p
.RT
.sp 1P
.LP
8
Abstract\(hyoperations
.sp 9p
.RT
.sp 1P
.LP
9
Abstract\(hyerrors
.sp 9p
.RT
.sp 2P
.LP
SECTION\ 3\ \(em\ \fIGeneral\(hyattribute\(hytypes and general\(hyauto\(hyaction\fR
.sp 1P
.RT
.sp 1P
.LP
10
Overview
.sp 9p
.RT
.sp 1P
.LP
11
General\(hyattribute\(hytypes
.sp 9p
.RT
.sp 1P
.LP
12
General\(hyauto\(hyaction\(hytypes
.sp 9p
.RT
.sp 2P
.LP
SECTION\ 4\ \(em\ \fIProcedures for message store and port realization\fR
.sp 1P
.RT
.sp 1P
.LP
13
Overview
.sp 9p
.RT
.sp 1P
.LP
14
Consumption of the message transfer system abstract\(hyservice
.sp 9p
.RT
.sp 1P
.LP
15
Supply of the message store abstract\(hyservice
.sp 9p
.RT
.sp 1P
.LP
16
Ports realization
.sp 9p
.RT
.sp 1P
.LP
\fIAnnex\ A\fR \(em
Formal assignment of object identifiers
.sp 9p
.RT
.LP
\fIAnnex\ B\fR \(em
Formal definition of the message store abstract\(hyservice
.LP
\fIAnnex\ C\fR \(em
Formal definition of general\(hyattribute\(hytypes
.LP
\fIAnnex\ D\fR \(em
Formal definition of general\(hyauto\(hyaction\(hytypes
.LP
\fIAnnex\ E\fR \(em
Formal definition of MS parameter upper bounds
.LP
\fIAnnex\ F\fR \(em
Example of the summarize abstract\(hyoperation
.LP
\fIAnnex\ G\fR \(em
Differences between the CCITT Recommendation X.413 Text
and ISO/IEC\ 10021\(hy5 Text.
.LP
.rs
.sp 13P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
SECTION\ 1\ \(em\ INTRODUCTION
.sp 1P
.RT
.sp 2P
.LP
\fB0\fR \fBIntroduction\fR
.sp 1P
.RT
.PP
This Recommendation is one of a series of Recommendations defining Message
Handling (MH) in a distributed open systems environment.
.PP
Message Handling provides for the exchange of messages between users on
a store\(hyand\(hyforward basis. A message submitted by one user (the originator)
is transferred through the message\(hytransfer\(hysystem (MTS) and delivered
to one or more other users (the recipients).
.PP
This Recommendation defines the message store abstract\(hyservice (MS
abstract\(hyservice) which supports message\(hyretrieval from a message
store (MS)
and indirect\(hymessage\(hysubmission through the MS in a message handling
system\ (MHS). The MS abstract\(hyservice also provides message\(hyadministration
services, as defined by the message transfer system (MTS) abstract\(hyservice.
.PP
This Recommendation has been produced by joint CCITT\(hyISO agreement.
The corresponding International Standard is ISO\ 10021\(hy5. Annex\ G list the
differences between the two documents.
.RT
.sp 2P
.LP
\fB1\fR \fBScope\fR
.sp 1P
.RT
.PP
This Recommendation defines the message store abstract\(hyservice.
This abstract\(hyservice is provided by the message store access\(hyprotocol
(specified in Recommendation\ X.419) in conjunction with the MTS
abstract\(hyservice (defined in Recommendations\ X.411), together with
the Remote Operations Service Element\ (ROSE) services (defined in Recommendation\
X.219). The abstract\(hysyntax\(hynotation for the application\(hylayer
protocols used in this Recommendation is defined in Recommendation\ X.208.
.PP
Other Recommendations define other aspects of the MHS.
Recommendation\ X.400 defines the user\(hyoriented services provided by
the MHS.
Recommendation\ X.402 provides an architectural overview of the MHS.
Recommenation\ X.407 provides a description of the abstract\(hyservice
definition conventions used in MHS. Recommendation\ X.420 defines the abstract\(hyservice
for interpersonal messaging and defines the format of interpersonal\(hymessages.
.PP
Section 2 of this Recommendation contains the message store
abstract\(hyservice definition. Paragraph\ 6 describes the MS model. Paragraph\
7
specifies the abstract\(hysyntax\(hynotation for the abstract\(hybind and the
abstract\(hyunbind\(hyoperations. Paragraph\ 8 specifies the abstract\(hysyntax\(hynotation
for the operations of the abstract\(hyservice. Paragraph\ 9 specifies the
abstract\(hysyntax\(hynotation for the errors of the abstract\(hyservice.
.PP
Section 3 of this Recommendation defines the general\(hyattribute\(hytypes
and general\(hyauto\(hyaction\(hytypes related to the MS. Paragraph\ 10
contains an
overview. Paragraph\ 11 specifies the abstract\(hysyntax\(hynotation for the
general\(hyattribute\(hytypes. Paragraph\ 12 specifies the abstract\(hysyntax\(hynotation
for the general\(hyauto\(hyaction\(hytypes.
.PP
Section 4 of this Recommendation describes the procedures for message store
and the ports realization. Paragraph\ 13 contains an overview.
Paragraph\ 14 describes how the message store abstract\(hyservice is supplied.
Paragraph\ 15 describes how the message transfer system abstract\(hyservice is
consumed. Paragraph\ 16 describes how the MS ports are realized.
.PP
No requirement is made for conformance to this Recommendation.
.RT
.sp 2P
.LP
\fB2\fR \fBReferences\fR
.sp 1P
.RT
.PP
For a list of references refer to Recommendation\ X.402.
.RT
.sp 2P
.LP
\fB3\fR \fBDefinitions\fR
.sp 1P
.RT
.sp 1P
.LP
3.1
\fICommon definitions for MHS\fR
.sp 9p
.RT
.PP
For a list of the common definitions for MHS refer to
Recommendation\ X.402.
.RT
.sp 1P
.LP
3.2
\fIMessage store definitions\fR
.sp 9p
.RT
.PP
For the purpose of this Recommendation the following definitions
apply:
.RT
.PP
3.2.1
\fBabstract\(hyassociation\fR \fB:\fR An abstract binding between two communication
partners, in this
Recommendation the binding between a UA and an MS for the provision of
the MS abstract\(hyservice, or between an MS and an MTA for the provision
of the MTS
abstract\(hyservice.
.bp
.sp 9p
.RT
.PP
3.2.2
\fBabstract\(hybind\(hyparameters\fR \fB:\fR Parameters defined in this
document which are contained in the
abstract\(hybind operations.
.sp 9p
.RT
.PP
3.2.3
\fBabstract\(hyunbind\(hyparameters\fR \fB:\fR Parameters defined in this
document which are contained in the
abstract\(hyunbind operation.
.sp 9p
.RT
.PP
3.2.4
\fBadministration port\fR \fB:\fR The port offering the administration
(for MTS) set of
abstract\(hyservice within the MS abstract\(hyservice.
.sp 9p
.RT
.PP
3.2.5
\fBalert abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation which
allows the MS to signal, based on
selection criteria, to the UA that messages or reports are waiting in the
MS. Can only be issued on an existing abstract\(hyassociation.
.sp 9p
.RT
.PP
3.2.6
\fBattribute\fR \fB:\fR The information of a particular type appearing
in an entry in an
information\(hybase.
.sp 9p
.RT
.PP
3.2.7
\fBattribute\(hytype\fR \fB:\fR That component of an attribute which indicates
the class of
information given by that attribute.
.sp 9p
.RT
.PP
3.2.8
\fBattribute\(hyvalue\fR \fB:\fR A particular instance of that class of
information indicated by an
attribute type.
.sp 9p
.RT
.PP
3.2.9
\fBattribute\(hyvalue\(hyassertion\fR \fB:\fR A proposition, which may
be true, false, or undefined, concerning
the values of attributes in an entry.
.sp 9p
.RT
.PP
3.2.10
\fBauto\(hyaction\fR \fB:\fR Actions, that can be performed automatically
by the MS, based on
previously registered information from the MS\(hyowner via the UA.
.sp 9p
.RT
.PP
3.2.11
\fBauto\(hyaction\(hytype\fR \fB:\fR An auto\(hyaction\(hytype is used
to indicate the type of auto\(hyaction,
e.g.\ alert.
.sp 9p
.RT
.PP
3.2.12
\fBauto\(hyalert\fR \fB:\fR Auto\(hyalert is the auto\(hyaction within
the MS, which triggers an
alert abstract\(hyoperation or another action by the MS.
.sp 9p
.RT
.PP
3.2.13
\fBauto\(hyforward\fR \fB:\fR Auto\(hyforward is the auto\(hyaction within
the MS, which triggers a
message to be auto\(hyforwarded to another recipient (or other recipients)
by the MS.
.sp 9p
.RT
.PP
3.2.14
\fBchild\(hyentry\fR \fB:\fR An entry, other than the main\(hyentry in
an information\(hybase. The
parent\(hyentry for a child\(hyentry can be either the main\(hyentry or another
child\(hyentry, depending on the number of entry levels in each case.
.sp 9p
.RT
.PP
3.2.15
\fBchild\(hysequence\(hynumber\fR \fB:\fR A sequence\(hynumber in a parent\(hyentry
pointing to a child\(hyentry. A
parent\(hyentry can have more than one child\(hysequence\(hynumber value,
depending on the number of child\(hyentries.
.sp 9p
.RT
.PP
3.2.16
\fBconditional (C) component\fR \fB:\fR An ASN.1 element which shall be
present in an instance of its
class as dictated by this Recommendation. See \fBgrade\fR .
.sp 9p
.RT
.PP
3.2.17
\fBcontent\(hylength\fR \fB:\fR An attribute which gives the length of
the content of a
delivered\(hymessage (or returned\(hycontent).
.sp 9p
.RT
.PP
3.2.18
\fBcontent\(hyreturned\fR \fB:\fR An attribute which signals that a delivered\(hyreport
(or a
delivered\(hymessage) contained a returned content.
.sp 9p
.RT
.PP
3.2.19
\fBconverted EITs\fR \fB:\fR An attribute identifying the encoded\(hyinformation\(hytypes
of the
message content after conversion.
.bp
.sp 9p
.RT
.PP
3.2.20
\fBcreation\(hytime\fR \fB:\fR An attribute which gives the creation\(hytime
(by the MS) of an
entry.
.sp 9p
.RT
.PP
3.2.21
\fBdelete abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation used
to delete one or more entries from an
information\(hybase.
.sp 9p
.RT
.PP
3.2.22
\fBdelivered\(hyEITs\fR \fB:\fR A multi\(hyvalued attribute, giving information
about EITs in a
delivered\(hymessage.
.sp 9p
.RT
.PP
3.2.23
\fBdelivered\(hymessage entry\fR \fB:\fR An entry in the stored\(hymessages
information\(hybase resulting from a
delivered\(hymessage.
.sp 9p
.RT
.PP
3.2.24
\fBdelivered\(hyreport entry\fR \fB:\fR An entry in the stored\(hymessages
information\(hybase resulting from a
delivered\(hyreport.
.sp 9p
.RT
.PP
3.2.25
\fBentry\fR \fB:\fR An information set in an information\(hybase. See main\(hyentry
and
child\(hyentry for further classification of entries.
.sp 9p
.RT
.PP
3.2.26
\fBentry\(hyinformation\fR \fB:\fR A parameter, used in abstract\(hyoperations,
which conveys selected
information from an entry.
.sp 9p
.RT
.PP
3.2.27
\fBentry\(hyinformation\(hyselection\fR \fB:\fR A parameter, used in abstract\(hyoperations,
which indicates what
information from an entry is being requested.
.sp 9p
.RT
.PP
3.2.28
\fBentry\(hystatus\fR \fB:\fR An attribute giving information about the
processing status of
that entry. Possible values are new, listed or processed.
.sp 9p
.RT
.PP
3.2.29
\fBentry\(hytype\fR \fB:\fR An attribute which signals an entry is associated
with a
delivered\(hymessage or a delivered\(hyreport.
.sp 9p
.RT
.PP
3.2.30
\fBfetch abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation which
allows one entry to be fetched from
the stored\(hymessages information\(hybase.
.sp 9p
.RT
.PP
3.2.31
\fBfetch\(hyrestrictions\fR \fB:\fR Restrictions, imposed by the UA, on
what kind of messages it is
prepared to receive as a result of fetch. The possible restrictions are on
message\(hylength, content\(hytypes and EITs.
.sp 9p
.RT
.PP
3.2.32
\fBfilter\fR \fB:\fR A parameter, used in abstract\(hyoperations, to test
a particular
entry in an information\(hybase and is either satisfied or not by that
entry.
.sp 9p
.RT
.PP
3.2.33
\fBfilter\(hyitem\fR \fB:\fR An assertion about the presence or value(s)
of an attribute of a
particular type in an entry under test. Each such assertion is either true
or false.
.sp 9p
.RT
.PP
3.2.34
\fBforwarding\(hyrequest\fR \fB:\fR This is a parameter that may be present
in a message\(hysubmission
abstract\(hyoperation, invoked by the UA, to request that a message is
forwarded from the MS.
.sp 9p
.RT
.PP
3.2.35
\fBgeneral\(hyattribute\fR \fB:\fR A set of MS attributes which are valid
for all types of messages
and reports, independent of content\(hytype. Only these MS attributes are
explicitly defined in this Recommendation.
.sp 9p
.RT
.PP
3.2.36
\fBgeneral\(hyauto\(hyaction\fR \fB:\fR Auto\(hyactions which are valid
for all types of messages and
reports, independent of content\(hytype. Only these auto\(hyactions are
explicitly
defined in this Recommendation.
.sp 9p
.RT
.PP
3.2.37
\fBGrade\fR \fB:\fR Defined in Recommendation X.402.
.sp 9p
.RT
.PP
3.2.38
\fBindirect\(hysubmission port\fR \fB:\fR The port offering the indirect\(hysubmission
abstract\(hyservice within
the MS abstract\(hyservice. The indirect\(hysubmission abstract\(hyservice
offers the
same services as the message\(hysubmission abtract\(hyservice (from the MTS
abstract\(hyservice) with the added functionality of forwarding messages
residing in the MS.
.bp
.sp 9p
.RT
.PP
3.2.39
\fBinformation\(hybase\fR \fB:\fR Objects within the MS which store information
relevant to the MS
abstract\(hyservice, e.g.\ the stored\(hymessages information\(hybase,
which stores the messages and reports that have been delivered into the
MS.
.sp 9p
.RT
.PP
3.2.40
\fBinformation\(hybase\(hytype\fR \fB:\fR The type of information\(hybase,
e.g. the stored\(hymessages.
.sp 9p
.RT
.PP
3.2.41
\fBlimit\fR \fB:\fR A component in the selector parameter which identifies
the maximum
number of selected entries to be returned in the result of an
abstract\(hyoperation.
.sp 9p
.RT
.PP
3.2.42
\fBlist abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation which
allows a selection of entries from an
information\(hybase and requested attribute information to be returned
for those entries.
.sp 9p
.RT
.PP
3.2.43
\fBlisted\fR \fB:\fR An entry\(hystatus value.
.sp 9p
.RT
.PP
3.2.44
\fBMacro\fR \fB:\fR See Recommendation X.208.
.sp 9p
.RT
.PP
3.2.45
\fBmain\(hyentry\fR \fB:\fR For each successful abstract\(hyoperation which
creates
information\(hybase entries, there is always one main\(hyentry. Further,
or more
detailed, information resulting from the same abstract\(hyoperation can
be stored in child\(hyentries.
.sp 9p
.RT
.PP
3.2.46
\fBmandatory (M) component\fR \fB:\fR An ASN.1 element which shall always
be present in an instance of
its class. See \fBgrade\fR .
.sp 9p
.RT
.PP
3.2.47
\fBmatching\fR \fB:\fR The process of comparing the value supplied in an
attribute\(hyvalue\(hyassertion with the value of the indicated attribute\(hytype
stored in the MS or deciding whether the indicated attribute\(hytype is
present.
.sp 9p
.RT
.PP
3.2.48
\fBmessage retrieval service element (MRSE)\fR \fB:\fR The application\(hyservice\(hyelement
by means of which a receiving UA
effects retrieval of messages from an MS, or any of various related
tasks.
.sp 9p
.RT
.PP
3.2.49
\fBMS\fR \fB:\fR Message store, also used as a shorter form for \*UMS
abstract\(hyservice\(hyprovider\*U.
.sp 9p
.RT
.PP
3.2.50
\fBMS abstract\(hyservice\fR \fB:\fR The set of capabilities that the MS
offers to its users by means
of its ports.
.sp 9p
.RT
.PP
3.2.51
\fBMS abstract\(hyservice\(hyuser\fR \fB:\fR The user of the MS abstract\(hyservice.
This is the UA.
.sp 9p
.RT
.PP
3.2.52
\fBMS abstract\(hyservice\(hyprovider\fR \fB:\fR The MS which provides
the MS abstract\(hyservice.
.sp 9p
.RT
.PP
3.2.53
\fBMS\(hyuser\fR \fB:\fR A shorter form for \*UMS abstract\(hyservice\(hyuser\*U.
.sp 9p
.RT
.PP
3.2.54
\fBmessage\(hysubmission abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation
which allows the UA to submit a message to
the MTS via the MS, and/or to forward a message from the MS to the MTS.
.sp 9p
.RT
.PP
3.2.55
\fBmulti\(hyvalued attribute\fR \fB:\fR An attribute which can have several
values associated with
it.
.sp 9p
.RT
.PP
3.2.56
\fBnew\fR \fB:\fR An entry\(hystatus value.
.sp 9p
.RT
.PP
3.2.57
\fBoptional (O) component\fR \fB:\fR An ASN.1 element which shall be present
in an instance of its
class at the discretion of the object (e.g.\ user) supplying that instance.
See \fBgrade\fR .
.sp 9p
.RT
.PP
3.2.58
\fBoriginal\(hyEITs\fR \fB:\fR An attribute identifying the original encoded\(hyinformation\(hytypes
of
the message content.
.sp 9p
.RT
.PP
3.2.59
\fBoverride\fR \fB:\fR A component of the selector parameter indicating
that the
previously registered\(hyrestrictions for this abstract\(hyoperation should
not apply for this instance of this abstract\(hyoperation.
.bp
.sp 9p
.RT
.PP
3.2.60
\fBparent\(hyentry\fR \fB:\fR A parent\(hyentry has one or more child\(hyentries,
which were created
as a result of the same abstract\(hyoperation. If a parent\(hyentry is not a
child\(hyentry of another parent\(hyentry, it is a main entry.
.sp 9p
.RT
.PP
3.2.61
\fBparent\(hysequence\(hynumber\fR \fB:\fR A sequence\(hynumber in a child\(hyentry
poiting to its parent\(hyentry.
There can only be one parent\(hysequence\(hynumber in a child\(hyentry.
.sp 9p
.RT
.PP
3.2.62
\fBpartial\(hyattribute\(hyrequest\fR \fB:\fR A component of the entry\(hyinformation\(hyselection
which enables the
return of only selected values of a multi\(hyvalued attribute.
.sp 9p
.RT
.PP
3.2.63
\fBposition\fR \fB:\fR Positions are parameters used to specify a bound
of a range.
.sp 9p
.RT
.PP
3.2.64
\fBprocessed\fR \fB:\fR An entry\(hystatus value.
.sp 9p
.RT
.PP
3.2.65
\fBrange\fR \fB:\fR A parameter, used in abstract\(hyoperations, to select
a contiguous
sequence of entries from an information\(hybase.
.sp 9p
.RT
.PP
3.2.66
\fBregister\(hyMS abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation
which allows the UA to register certain
information, relevant to the UA\(hyMS interworking, in the MS.
.sp 9p
.RT
.PP
3.2.67
\fBregistration\fR \fB:\fR Information which is registered in the MS and
stored (until
changed by the Register\(hyMS abstract\(hyoperation) between abstract\(hyassociations.
(See Register\(hyMS).
.sp 9p
.RT
.PP
3.2.68
\fBregistration\(hyidentifier\fR \fB:\fR An identifier for one particular
set of registration\(hyparameters
for an auto\(hyaction\(hytype.
.sp 9p
.RT
.PP
3.2.69
\fBretrieval port\fR \fB:\fR The port offering the retrieval set of abstract\(hyservices
within
the MS abstract\(hyservice.
.sp 9p
.RT
.PP
3.2.70
\fBreturned\(hycontent entry\fR \fB:\fR An entry\(hytype in the stored\(hymessages
information\(hybase which
contains the returned content from a previously submitted message.
.sp 9p
.RT
.PP
3.2.71
\fBselector\fR \fB:\fR A parameter, used in abstract\(hyoperations, to
select entries from
an information\(hybase.
.sp 9p
.RT
.PP
3.2.72
\fBsequence\(hynumber\fR \fB:\fR An attribute which uniquely identifies
an entry. Sequence\(hynumbers
are allocated in ascending order.
.sp 9p
.RT
.PP
3.2.73
\fBsingle\(hyvalued attribute\fR \fB:\fR An attribute which can only have
one value associated with
it.
.sp 9p
.RT
.PP
3.2.74
\fBspan\fR \fB:\fR A component in the summarize abstract\(hyoperation result
containing
the lowest and highest sequence\(hynumbers of the entries that matched the
selection criteria.
.sp 9p
.RT
.PP
3.2.75
\fBstored\(hymessages\fR \fB:\fR The most important information\(hybase
in this Recommendation, used
to store entries containing messages and reports delivered by the MTS to the
MS.
.sp 9p
.RT
.PP
3.2.76
\fBsubscription\fR \fB:\fR A long\(hyterm agreement between the MS supplier
or administrator and
the MS customers (MS\(hyowners) on the availability and use of optional MS
features such as optional services and attributes. This Recommendation,
assumes that such a mechanism is provided, but does not prescribe or offer
any
standardized method for how to provide this.
.sp 9p
.RT
.PP
3.2.77
\fBsubstring\fR \fB:\fR A filter\(hyitem used to specify string of characters
which appear
(in the same given order) in a value of an attribute.
.sp 9p
.RT
.PP
3.2.78
\fBsummarize abstract\(hyoperation\fR \fB:\fR An abstract\(hyoperation
which allows a quick overview of the kind
and number of entries which are currently stored in an information\(hybase.
.bp
.sp 9p
.RT
.PP
3.2.79
\fBsynopsis\fR \fB:\fR A content specific attribute that may be used to
show how
child\(hyentries, containing parts of the content, are related to each
other and the main\(hyentry. The attribute has to be specified in the Recommendation,
which describes the content\(hytype, e.g.\ see IPM\(hysynopsis defined
in
Recommendation\ X.420.
.sp 9p
.RT
.sp 2P
.LP
\fB4\fR \fBAbbreviations\fR
.sp 1P
.RT
.PP
For a list of abbreviations refer to Recommendation\ X.402.
.RT
.sp 2P
.LP
\fB5\fR \fBConventions\fR
.sp 1P
.RT
.PP
This Recommendation uses the description conventions listed in the following
four paragraphs.
.RT
.sp 1P
.LP
5.1
\fIConventions for abstract\(hyservices\fR
.sp 9p
.RT
.PP
This Recommendation uses the following ASN.1\(hybased descriptive
conventions for the indicated purposes:
.RT
.LP
1)
ASN.1 itself, to specify the abstract\(hysyntax of
information\(hybases and their components, and common data\(hytypes.
.LP
2)
The ASN.1 PORT macro and associated abstract\(hyservice
definition conventions of Recommendation\ X.407, to specify the retrieval
port.
.LP
3)
The ASN.1 ABSTRACT\(hyBIND, ABSTRACT\(hyUNBIND,
ABSTRACT\(hyOPERATION, and ABSTRACT\(hyERROR macros and associated abstract\(hyservice
definition conventions of Recommendation\ X.407, to specify the MS
abstract\(hyservice.
.PP
Whenever this Recommendation describes a class data structure
having components, each component is categorized as one of the following
\fBgrade\fR :
.LP
1)
\fBMandatory\fR (M)\ \(em\ A mandatory component shall be present in
every instance of the class.
.LP
2)
\fBOptional\fR (O)\ \(em\ An optional component shall be present in an
instance of the class at the discretion of the object (e.g.\ user) supplying
that instance.
.LP
3)
\fBConditional\fR (C)\ \(em\ A conditional component shall be present
in an instance of the class as dictated by this Recommendation.
.sp 1P
.LP
5.2
\fIConventions for attribute\(hytypes used in Table\ 1/X.413 (\(sc\ 11)\fR
.sp 9p
.RT
.PP
This Recommendation uses the conventions listed below in its
definition of the attribute\(hytypes for the MS abstract\(hyservice.
.PP
For the column headed \fISingle/Multi\(hyvalued\fR \| the following values
can occur:
.RT
.LP
S
single\(hyvalued
.LP
M
multi\(hyvalued
.PP
For the column headed \fISupport level by the MS and access UA\fR \| the
following values can occur:
.LP
M
mandatory
.LP
O
optional
.PP
For the columns headed \fIPresence in delivered message entry\fR ,
\fIPresence in delivered report entry\fR , and \fIPresence in returned
message entry\fR , \|the presence of each attribute\(hytype is described
by one of the following
values:
.LP
P
\fIalways present\fR \| in the entry because:
.LP
\(em
it is mandatory for generation by the MS; or
.LP
\(em
it is a mandatory or defaulted parameter in the
relevant abstract\(hyoperation.
.LP
C
\fIconditionally present\fR \| in the entry. It would be present
because:
.LP
\(em
it is supported by the MS and subscribed to by the user and;
.LP
\(em
it was present in an optional parameter in the relevant abstract\(hyoperation.
.LP
\(em
\fIalways absent\fR ,\| otherwise.
.bp
.PP
For the columns headed \fIAvailable for list, alert\fR \| and
\fIavailable for summarize\fR ,\| the following values can occur:
.LP
N
no
.LP
Y
yes
.sp 1P
.LP
5.3
\fIConventions for attribute\(hytypes used in Table\ 2/X.413 of (\(sc\ 11)\fR
.sp 9p
.RT
.PP
This Recommendation uses the conventions listed below in its
definition of the attribute\(hytype for the MS abstract\(hyservice. Paragraph\
11
includes Table\ 2/X.413 that lists the attribute\(hytypes.
.PP
For the column headed \fIsingle/multi\(hyvalued\fR \| the following values
can occur:
.RT
.LP
S
single\(hyvalued
.LP
M
multi\(hyvalued
.PP
For the column headed \fISource generated by\fR \| the following values
can occur:
.LP
MD
MessageDelivery abstract\(hyoperation
.LP
MS
MessageStore
.LP
RD
ReportDelivery abstract\(hyoperation
.sp 1P
.LP
5.4
\fIFont conventions for text in general\fR
.sp 9p
.RT
.PP
Throughout this Recommendation, terms are rendered in \fBbold\fR when defined,
without emphasis upon all other occasions. Terms that are proper nouns
are capitalized, generic terms are not. Multi\(hyword generic terms are
hyphenated.
.RT
.sp 1P
.LP
5.5
\fIFont conventions for ASN.1 definitions\fR
.sp 9p
.RT
.PP
Throughout this Recommendation, ASN.1 definitions are written in a different
(\fBbold\fR ) font than the rest of the document in order to highlight
the difference between normal text and ASN.1 definitions. The font used
for ASN.1 definitions is also one size smaller than the ordinary text.
When ASN.1
protocol elements and elements values are described in accompanying text,
their names are rendered in \fBbold\fR .
.RT
.sp 1P
.LP
5.6
\fIRules for ASN.1 definitions\fR
.sp 9p
.RT
.PP
ASN.1 definitions appears both in the body of the document to aid the exposition,
and again, formally in Annexes for reference. If differences
are found between the ASN.1 used in the exposition and that formally defined
in the correspoding Annex, a specified error is indicated.
.RT
.LP
.rs
.sp 16P
.ad r
Blanc
.ad b
.RT
.LP
.bp
.LP
SECTION\ 2\ \(em\
MESSAGE STORE ABSTRACT\(hySERVICE DEFINITION
.sp 1P
.RT
.sp 2P
.LP
\fB6\fR \fBMessage store model\fR
.sp 1P
.RT
.PP
The message store (MS) is modeled as an atomic object, wich acts
as a provider of services to an MS abstract\(hyservice\(hyuser (i.e., a
user agent), and a user of the services provided by the message transfer
system (MTS).
.PP
The MS serves an intermediary role between the UA and the MTS. Its
primary function is to accept delivery of messages on behalf of a single MHS
end\(hyuser, and to retain them for subsequent retrieval by the end\(hyuser's
UA.
The MS also provides indirect message\(hysubmission and message\(hyadministration
services to the UA, in effect, via \*Qpass\(hythrough\*U to the MTS. This
enables the MS to provide additional functionality compared to submission
directly to the MTA; such a forwarding of messages residing in the MS.
.PP
Like the UA, the MS acts on behalf of only a single MHS end\(hyuser;
i.e. it does not provide common or shared multi\(hyuser MS service.
.PP
The MS is described using an abstract model in order to define the
sevices provided by the MS \(em the Message Store abstract\(hyservice.
Figure\ 1/X.413 shows the MS abstract\(hyservice in relation to its user
and to the Message
Transfer System abstract\(hyservice. In this figure, the open boxes represent
the consumption of the abstract service, and the closed boxes represent
the supply of the abstract service.
.RT
.LP
.rs
.sp 15P
.ad r
\fBFigure 1/X.413, p. \fR
.sp 1P
.RT
.ad b
.RT
.PP
For an introduction and description of the abstract\(hyservice
concept and its definition conventions, see Recommendation\ X.407.
.PP
In secure messaging the MS is treated as a separate object with a
unique identity and has separate key (or a set of keys) to the UA.
.RT
.sp 1P
.LP
6.1
\fIMessage store object\fR
.sp 9p
.RT
.PP
The MS is modeled as an atomic object. It supplies the MS Retrieval Port
abstract\(hyservices to the MS abstract\(hyservice\(hyuser. Acting as a
\*Qsurrogate\*U MTS abstract\(hyservice\(hyprovider, the MS also supplies
the MTS submission and
administration abstract\(hyservice to the MS abstract\(hyservice\(hyuser
(MS\(hyuser), and acting as a UA \*Qsurrogate\*U, it consumes the MTS delivery
port, submission
port, and administration port abstract\(hyservices in its role as MTS
abstract\(hyservice user.
.PP
The formal definition for the message store object is as follows:
.RT
.LP
mS OBJECT
.LP
PORTS\|{\|retrieval[S],
.LP
indirectSubmission[S],
.LP
administration[S],
.LP
delivery[C],
.LP
submission[C],
.LP
administration[C]}
.LP
::= id\(hyot\(hyms
.bp
.PP
The MS\(hyuser is also modeled as an object. It consumes the MS
Retrieval Port and Indirect\(hysubmission Port abstract\(hyservices and the
Administration Port abstract\(hyservices provided transparently by the MS.
.LP
msUser OBJECT
.LP
PORTS\|{\|retrieval[C],
.LP
indirectSubmission[C],
.LP
administration[C]}
.LP
::= id\(hyot\(hyms\(hyuser
.sp 1P
.LP
6.2
\fIMessage store ports\fR
.sp 9p
.RT
.PP
An MS provides the retrieval, indirect\(hysubmission, and
administration ports to the MS abstract\(hyservice user. The collection of
capabilities provided by these port provides the MS abstract\(hyservice. The
retrieval capabilities are unique to the MS. These capabilities include
obtaining information on, fetching (in whole or in part), and deleting
messages residing in the MS. Additional capabilities are provided for registering
certain MS provided automatic actions (i.e., auto\(hyforwarding and alert).
.PP
\fINote\fR \ \(em\ ISO are planning to define additional message management
services performed by the MS on the UA's behalf, for logging incoming and
outgoing messages, and for auto\(hycorrelating incoming notifications with
logging information about outgoing messages. These are outside the scope
of this CCITT Recommendation.
.PP
In order to provide the services described in\ \(sc\ 6.1 to an MS\(hyuser,
the MS interacts, on behalf of the MS\(hyuser, with the MTS abstract\(hyservice,
and acts as a consumer of the MTS delivery, submission and administration
ports. The
abstract\(hyservices provided by the MTS ports are defined in clause\ 8 of
Recommendation\ X.411.
.PP
By means of the abstract\(hybind operation, the MS authenticates an
MS\(hyuser before providing it with any of the above retrieval capabilities.
Similarly, the MTS abstract\(hyservices must authenticate the MTS abstract\(hyservice
user before extending its services to the MTS abstract\(hyservice\(hyuser.
.PP
With the exception of the retrieval port provided alert service and
the indirect\(hysubmission port provided submission\(hycontrol service, all the
services provided by the MS abstract\(hyservice are invoked by the MS\(hyuser
and
performed by the MS.
.PP
Security\(hylabels may be assigned to the MS in line with the
security\(hypolicy in force. The security\(hypolicy may also define how
security\(hylabels are to be used to enforce the security\(hypolicy. If
security\(hylabels are assigned to the MS, the handling of stored messages and
reports are not assigned to the MS, the handling of stored\(hymessages and
reports is discretionary.
.PP
If security\(hycontexts are established between the UA and the MS, and
between the MS and the MTA, the security\(hylabel that is assigned to a
message or probe is confined by the security\(hycontext in line with the
security\(hypolicy in force. If security\(hycontexts are not established
the assignment of a
message\(hysecurity\(hylabel to a message or probe is at the discretion of the
originator.
.RT
.sp 1P
.LP
6.2.1
\fIRetrieval port\fR
.sp 9p
.RT
.PP
The \fBretrieval port\fR is defined as follows:
.RT
.LP
retrievalPORT
.LP
CONSUMER INVOKES{
.LP
\ \ Summarize,
.LP
\ \ List,
.LP
\ \ Fetch,
.LP
\ \ Delete,
.LP
\ \ Register\(hyMS}
.LP
SUPPLIER INVOKES{
.LP
\ \ Alert}
.LP
::= id\(hypt\(hyretrieval
.PP
The details of the \fBretrieval port\fR abstract\(hyservices are
described in\ \(sc\(sc\ 7 to\ 9.
.sp 1P
.LP
6.2.2
\fIIndirect\(hysubmission port\fR
.sp 9p
.RT
.PP
The \fBindirect\(hysubmission port\fR is defined as follows:
.RT
.LP
indirectSubmissionPORT ::= submission
.PP
The \fBindirect\(hysubmission port\fR makes use of the submission port
abstract\(hyservices defined in\ \(sc\ 8.2 of Recommendation\ X.411.
.bp
.sp 1P
.LP
6.2.3
\fIAdministration port\fR
.sp 9p
.RT
.PP
The \fBadministration port\fR is defined in\ \(sc\ 8.4 of
Recommendation\ X.411.
.PP
The MS shall have no interaction with the change\(hycredentials
abstract\(hyservice. If the MS\(hyuser needs to have its credentials updated,
then
the register\(hyMS abstract\(hyoperation is used. See\ \(sc\ 8.6.
.RT
.sp 1P
.LP
6.3
\fIInformation model\fR
.sp 9p
.RT
.PP
This paragraph describes the information model used by the MS. It models
\fBinformation\(hybases\fR , which consist of \fBentries\fR , which consist
of
\fBattributes\fR .
.RT
.sp 1P
.LP
6.3.1
\fIInformation\(hybases\fR
.sp 9p
.RT
.PP
The MS stores and maintains \fBinformation\(hybases\fR in the MS is a
\*Qdata\(hybase\*U containing all the \fBentries\fR representing constituent
objects of a particular category or categories.
.PP
This Recommendation defines and describes the \fBstored\(hymessages
information\(hybase\fR . This holds information derived from message\(hydeliveries
and report\(hydeliveries to the MS across the MTS Delivery Port, and is
described
in\ \(sc\ 6.4.
.PP
\fINote\fR \ \(em\ A future Addendum to the corresponding Part of the ISO
Standard will define additional information\(hybases for logging, called
the inlog and outlog, which are outside the scope of this CCITT Recommendation.
.RT
.LP
informationBase ::= INTEGER{
.LP
stored\(hymessages
(0),
.LP
inlog
(1),
.LP
outlog
(2)\|}\|(0\|.\|.\|ub\(hyinformation\(hybases)
.sp 1P
.LP
6.3.2
\fIEntries\fR
.sp 9p
.RT
.PP
Each \fBinformation\(hybase\fR is organized as a sequence of \fBentries\fR
. An \fBentry\fR represents a single object (such as a delivered message)
within the
\fBinformation\(hybase\fR .
.PP
Each entry is identified by means of its \fBsequence\(hynumber\fR , unique
within an \fBinformation\(hybase\fR , and generated by the MS as new entries
are
created. Within an \fBinformation\(hybase\fR , the MS generates the \fBsequence\(hynumbers\fR
in ascending order without cycling, and they are never re\(hyused.
.RT
.LP
SequenceNumber ::= INTEGER (0\|.\|.\|ub\(hymessages)
.PP
\fINote\fR \ \(em\ For example, the MS may choose to allocate
\fBsequence\(hynumbers\fR by using the time to a sufficient granularity
to ensure
uniqueness.
.sp 2P
.LP
6.3.3
\fIAttributes\fR
.sp 1P
.RT
.sp 1P
.LP
6.3.3.1
\fIIntroduction\fR
.sp 9p
.RT
.PP
An \fBentry\fR consists of a set of \fBattributes\fR . This is depicted
in Figure\ 2/X.413.
.PP
Each \fBattribute\fR provides a piece of information about, or derived
from, the data to which the \fBentry\fR corresponds. One such piece of
information is the \fBsequence\(hynumber\fR of the \fBentry\fR itself,
and another is the
\fBcreation\(hytime\fR .
.PP
An \fBattribute\fR consists of an \fBattribute\(hytype\fR , which identifies
the class of information given by an \fBattribute\fR , and the corresponding
\fBattribute\(hyvalue(s)\fR , which are particular instances of that class
appearing
in the \fBentry\fR .
.RT
.LP
Attribute ::= SEQUENCE{
.LP
type
AttributeType,
.LP
values
SEQUENCE SIZE
(1\|.\|.\|ub\(hyattribute\(hyvalues) OF ANY\|\(hy\(hy\fIDEFINED BY\fR \fItype\fR
\|\(hy\(hy}
.PP
\fINote\fR \ \(em\ Thus, for example, in a delivered\(hymessage\(hyentry
(described in\ \(sc\ 6.4) the \fBattribute\(hytype\fR could be the message's
\fBpriority\fR ,
and a corresponding \fBattribute\(hyvalue\fR could be \fBurgent\fR .
.PP
All \fBattributes\fR in an \fBentry\fR must be of distinct
\fBattribute\(hytypes\fR .
.PP
For some \fBattribute\(hytypes\fR , an \fBattribute\fR may only contain
a single \fBattribute\(hyvalue\fR . Such an \fBattribute\(hytype\fR is
said to be \fBsingle\(hyvalued\fR . For others, an \fBattribute\fR may
contain one or more \fBattribute\(hyvalues\fR , all of the same ASN.1 data\(hytype.
Such an \fBattribute\(hytype\fR is said to be \fBmulti\(hyvalued\fR .
Whether an \fBattribute\(hytype\fR is \fBsingle\(hyvalued\fR or \fBmulti\(hyvalued\fR
is stated when the \fBattribute\(hytype\fR is defined (see\ \(sc\ 6.3.3.2).
.PP
\fINote\ 2\fR \ \(em\ Thus, for example, the \fBattribute\(hytype\fR for the
\fBoriginator\(hyname attribute\fR (described in\ \(sc\ 11.2.28) is \fBsingle\(hyvalued\fR
,
whereas that for \fBother\(hyrecipient\(hynames\fR (described in\ \(sc\
11.2.29) is
\fBmulti\(hyvalued\fR .
.bp
.RT
.LP
.rs
.sp 23P
.ad r
\fBFigure 2/X.413, p.\fR
.sp 1P
.RT
.ad b
.RT
.sp 1P
.LP
6.3.3.2
\fIAttribute\(hytype\fR
.sp 9p
.RT
.PP
Some \fBattribute\(hytypes\fR will be internationally standardized. Other
\fBattribute\(hytypes\fR will be defined by national administrative authorities
and
private organizations. This implies that a number of separate authorities
will be responsible for assigning types in a way that ensures that each is
distinct from all other assigned types. This is accomplished by identifying
each \fBattribute\(hytype\fR with an object\(hyidentifier when the \fBattribute\(hytype\fR
is
defined.
.RT
.LP
AttributeType ::= OBJECT IDENTIFIER
.PP
Certain general\(hypurpose \fBattribute\(hytypes\fR for the stored\(hymessages
information\(hybase are defined in\ \(sc\ 11. Such \fBattribute\(hytypes\fR
are known as
\fBgeneral\(hyattribute\(hytypes\fR and attributes of these types as
\fBgeneral\(hyattributes\fR .
.sp 1P
.LP
6.3.3.3
\fIAttribute\(hyvalues\fR
.sp 9p
.RT
.PP
Defining an \fBattribute\(hytype\fR also involves specifying the ASN.1
data\(hytype to which every value in such attributes must conform. The
data\(hytype of an \fBattribute\(hyvalue\fR for the \fBattribute\(hytype\fR
is defined through the
object\(hyidentifier for the \fBattribute\(hytype\fR .
.RT
.sp 1P
.LP
6.3.3.4
\fIAttribute\(hytype definition and the ATTRIBUTE macro\fR
.sp 9p
.RT
.PP
The definition of an \fBattribute\(hytype\fR involves:
.RT
.LP
a)
assigning an object\(hyidentifier to the \fBattribute\(hytype\fR ;
.LP
b)
indicating the ASN.1 data\(hytype of an \fBattribute\(hyvalue\fR ;
.LP
c)
indicating whether an \fBattribute\fR of this
\fBattribute\(hytype\fR may have more than one value;
.LP
d)
indicating whether an \fBattribute\fR of this \fBattribute\(hytype\fR
may be used for filtering based on equality, substrings, and/or ordering
relations (see\ \(sc\ 8.1.2).
.bp
.PP
\fINote\fR \ \(em\ A filter may always test for the presence or absence
in an entry of an \fBattribute\fR of a particular \fBattribute\(hytype\fR
.
.PP
The following ASN.1 macro is used to define an \fBattribute\(hytype\fR
. The formal definition of this macro is given in Recommendation\ X.501
and is
documented here as an aid to the reader.
.RT
.LP
ATTRIBUTE MACRO ::=
.LP
BEGIN
.LP
TYPE NOTATION
::=
AttributeSyntax Multivalued\||\|empty
.LP
VALUE NOTATION
::=
value (VALUE OBJECT IDENTIFIER)
.LP
AttributeSyntax
::=
\*QWITH ATTRIBUTE\(hySYNTAX\*U SyntaxChoice
.LP
SyntaxChoice
::=
value
(ATTRIBUTE\(hySYNTAX) Constraint\||\|type MatchTypes
.LP
Constraint
::=
\*Q(\*Q ConstraintAlternative \*U)\*U\||\|empty
.LP
ConstraintAlternative
::=
StringConstraint\||\|IntegerConstraint
.LP
StringConstraint
::=
\*QSIZE\*U \*Q(\*Q SizeConstraint \*U)\*U\||\|empty
.LP
SizeConstraint
::=
SingleValue\||\|Range
.LP
SingleValue
::=
value (INTEGER)
.LP
Range
::=
value (INTEGER) \*Q..\*U value (INTEGER)
.LP
IntegerConstraint
::=
\*Q(\*Q Range \*U)\*U
.LP
MatchTypes
::=
\*QMATCHES FOR\*U Matches\||\|empty
.LP
Matches
::=
Match Matches\||\|Match
.LP
Match
::=
\*QEQUALITY\*U\||\|\*QSUBSTRINGS\*U\||\|\*QORDERING\*U
.LP
Multivalued
::=
\*QSINGLE VALUE\*U\||\|\*QMULTIVALUE\*U\||\|empty
.LP
END
.PP
The correspondence between the parts of the definition, as listed above,
and the various pieces of the notation introduced by the \fBATTRIBUTE\fR
macro, is as follows:
.LP
a)
\fBMACRO value\fR : The \fBobject\(hyidentifier\fR which is used to
identify an attribute.
.LP
b)
\fBAttribute\(hysyntax\fR : Notes which syntax\(hychoice has been
made.
.LP
c)
\fBSyntax\(hychoice\fR : Notes whether the attribute is defined
externally or internally. The syntax of all the attributes defined in this
[Recommendation Part of the Standard] is defined internally, which means
using the choice \fBtypeMatchTypes\fR .
.LP
d)
\fBMultivalued\fR : denotes whether the attribute is single or
multi\(hyvalued.
.LP
e)
\fBMatch\(hytypes\fR : Gives the data\(hytype of the contents of the
attribute, and describes whether the \fBattributes\fR can be matched \fB(\*QMATCHES
FOR\*U)\fR for \fBequality (\*QEQUALITY\*U)\fR , for \fBsubstrings (\*QSUBSTRINGS\*U)\fR
, and for an \fBordering\fR relation \fB(\*QORDERING\*U)\fR . If the production
is empty, then no
matching rules are defined.
.PP
Matching for this Recommendation is restricted as follows:
.LP
i)
\fBEQUALITY\fR is applicable to any attribute\(hysyntax. The
presented value must conform to the data\(hytype of the attribute\(hysyntax;
.LP
ii)
\fBSUBSTRING\fR is applicable to any attribute\(hysyntax with a
\fBstring\fR data type. The presented value must be a sequence (\*QSEQUENCE
OF\*U),
each of whose elements conforms to the data\(hytype, and
.LP
iii)
\fBORDERING\fR is applicable to any attribute\(hysytanx for which a rule
can be defined that will allow a presented value to be described as less
than equal to, or greater than a target value. The presented value must
conform to the data\(hytype of the attribute\(hysyntax. MS uses this for
the INTEGER and
UTCTime data types. For UTCTime, the ordering is chronological, not
alphabetical.
.PP
The remaining choices and parameters of the \fBATTRIBUTE\fR macro are not
used in this Recommendation.
.sp 1P
.LP
6.3.4
\fIMain\(hyentries, parent\(hyentries, and child\(hyentries\fR
.sp 9p
.RT
.PP
Although entries in a single information\(hybase are generally
independent of each other, the MS information model allows such \fBentries\fR
to be related to one another. One entry, a \fBchild\(hyentry\fR , may be
the child of
another, its \fBparent\(hyentry\fR , in a tree\(hystructured relationship.
An entry which is not a \fBchild\(hyentry\fR is termed a \fBmain\(hyentry\fR
.
.bp
.PP
This relationship is recorded by means of two special
\fBgeneral\(hyattributes\fR :
.RT
.LP
a)
\fBparent\(hysequence\(hynumber\fR : This single\(hyvalued attribute
gives the sequence\(hynumber of a \fBchild\(hyentry\fR 's \fBparent\(hyentry\fR
. It is absent from a
\fBmain\(hyentry\fR . Its definition is given in\ \(sc\ 11.2.30.
.LP
b)
\fBchild\(hysequence\(hynumbers\fR : This multi\(hyvalued attribute gives
the sequence\(hynumbers of all the \fBchild\(hyentries\fR of a \fBparent\(hyentry\fR
. It is
absent from an entry which is not a \fBparent\(hyentry\fR . Its definition
is given
in\ \(sc\ 11.2.1.
.PP
The abstract\(hyoperations of the MS abstract\(hyservice (see\ \(sc\ 8)
act by default only on \fBmain\(hyentries\fR . Some may be directed to
act on all entries, both \fBmain\(hyentries\fR and \fBchild\(hyentries\fR
. In particular, the argument of a
delete abstract\(hyoperation (see\ \(sc\ 8.5) may only select \fBmain\(hyentries\fR
, in which case the \fBmain\(hyentry\fR and all its children and children's
children, etc., will also be deleted.
.PP
\fINote\fR \ \(em\ This concept allows, for example, those body\(hyparts of an
interpersonal message which contain a forwarded message (for details see\
\(sc\ 19.1 of Recommendation\ X.420) to be represented by individual \fBchild\(hyentries\fR
. The \fBcontent general\(hyattribute\fR of the \fBmain\(hyentry\fR will
comprise the complete
\fBcontent\fR , so the data representing that message \fBbody\(hypart\fR
is logically
present in more than one \fBentry\fR .
.RT
.sp 1P
.LP
6.4
\fIStored\(hymessages\fR
.sp 9p
.RT
.PP
The \fBstored\(hymessages information\(hybase\fR acts as a repository for
information obtained from the Message
Delivery and ReportDelivery
abstract\(hyoperation of the DeliveryPort. It contains entries for delivered
messages (\fBdelivered\(hymessage\(hyentries\fR ), of an open\(hyended
number of
content\(hytypes, and for reports (\fBdelivered\(hyreport\(hyentries\fR
). An entry in the
\fBstored\(hymessage\(hyinformation\(hybase\fR is created by the MS when
a message or report is delivered to the MS. For more details of these entries
and how they are
generated, see\ \(sc\(sc\ 11 and\ 15.
.PP
To draw information from the content of a message, the MS must know
the content's syntax and semantics, as signaled via the content\(hytype. In
general, a particular instance of the MS has knowledge of zero or more
content\(hytypes. When an MS encounters a message of whose content\(hytype
it has
insufficient knowledge, it is unable to generate any content\(hytype\(hyspecific
attributes in the message's entry.
.PP
A delivered\(hymessage or an arriving notification may result in a
main\(hyentry and one or more levels of child\(hyentries. The one case
defined by
this Recommendation is when a non\(hydelivery notification contains a
returned\(hycontent (the \fBdelivered\(hyreport\(hyentry\fR is the main\(hyentry
and the
returned\(hycontent is its child\(hyentry, known as a \fBreturned\(hycontent
entry\fR ).
.PP
The rules for how a message\(hycontent may be split across several
entries is specific to each content\(hytype. A content\(hyspecific
\fBsynopsis\(hyattribute\fR may be used to show how the main\(hyentry and the
corresponding child\(hyentries are related. When such an attribute is defined,
it appears in the Recommendation which defines the content\(hytype itself.
The
\fBsynopsis\(hyattribute\fR is constructed by the MS.
.PP
\fINote\fR \ \(em\ For Interpersonal Messaging (Recommendation\ X.420), nested
IP\(hymessages within an IP\(hymessage are each represented by a child\(hyentry.
The
ipm\(hysynopsis attribute\(hytype is an example of a content\(hyspecific
\fBsynopsis\(hyattribute\(hytype\fR .
.PP
An important property of an entry in the stored\(hymessages is its
\fBentry\(hystatus\fR . It is created and maintained by the MS. It can take the
following values:
.RT
.LP
a)
\fBNew\fR \ \(em\ The message has neither been \fBlisted\fR by a UA nor
has it been automatically processed by the MS.
.LP
b)
\fBListed\fR \ \(em\ Information about the message has been returned
to the UA in either a list abstract\(hyoperation or a fetch abstract\(hyoperation,
but the message has not yet been completely \fBprocessed\fR .
.LP
c)
\fBProcessed\fR \ \(em\ Either a UA has \*Qcompletely fetched\*U the
message, or the MS has performed some auto\(hyaction on it. (Note that some
auto\(hyactions result in the message being deleted). The exact definition of
\*Qcompletely fetched\*U is content\(hyspecific and is defined in the corresponding
content\(hyspecific Recommendation.
.LP
The \fBentry\(hystatus\fR of a (non\(hy)delivery\(hynotification becomes
\fBprocessed\fR when the delivered\(hyreport\(hyenvelope is retrieved.
.PP
The definition for \fBentry\(hystatus\fR is as follows:
.LP
EntryStatus ::= INTEGER {
.LP
new
(0),
.LP
listed
(1),
.LP
processed
(2)}
.bp
.sp 2P
.LP
6.5
\fIAuto\(hyactions\fR
.sp 1P
.RT
.sp 1P
.LP
6.5.1
\fIIntroduction\fR
.sp 9p
.RT
.PP
This paragraph defines a framework for automatic actions
(\fBauto\(hyactions\fR ) which may be registered with the MS.
.PP
An \fBauto\(hyaction\fR is an action that will occur automatically whenever
the associated registration criteria have been satisfied. The result of
an
action being invoked is visible externally to the MS. \fBAuto\(hyactions\fR are
registered in the MS using the Register\(hyMS abstract\(hyoperation (see
\(sc\ 8.6).
.PP
Each class of \fBauto\(hyaction\fR is identified by means of an
\fBauto\(hyaction\(hytype\fR . Associated with the registration of an \fBauto\(hyaction\fR
, there is a corresponding \fBauto\(hyaction\(hyregistration\(hyparameter\fR
, which are the
parameters needed by the MS to perform the registered \fBauto\(hyaction\fR
automatically. The registration of an \fBauto\(hyaction\fR requires the
use of an
\fBauto\(hyaction\(hyregistration\(hyidentifier\fR to identify the particular
registration.
.RT
.LP
AutoActionRegistration ::= SEQUENCE\|{
.LP
type
AutoActionType,
.LP
registration\(hyidentifier
[0]\ INTEGER
(1\|.\|.\|ub\(hyper\(hyauto\(hyaction)DEFAULT1,
.LP
registration\(hyparameter
[1]\ ANY DEFINED BY
type\|}
.sp 1P
.LP
6.5.2
\fIAuto\(hyaction\(hytype\fR
.sp 9p
.RT
.PP
Some \fBauto\(hyaction\(hytypes\fR will be internationally standardized.
Other \fBauto\(hyaction\(hytypes\fR will be defined by national administrative
authorities and private organizations. This implies that a number of separate
authorities will be responsible for assigning types in a way that ensures
that each is distinct from all other assigned \fBauto\(hyaction\(hytypes\fR
. This is
accomplished by identifying each \fBauto\(hyaction\(hytype\fR with an object
identifier when the \fBauto\(hyaction\(hytype\fR is defined.
.RT
.LP
AutoActionType ::= OBJECT IDENTIFIER
.PP
Certain general\(hypurpose \fBauto\(hyaction\(hytypes\fR are defined in
\(sc\ 12. Such \fBauto\(hyaction\(hytypes\fR are known as \fBgeneral\(hyauto\(hyaction\(hytypes\fR
and \fBauto\(hyactions\fR of these types as \fBgeneral\(hyauto\(hyactions\fR .
.sp 1P
.LP
6.5.3
\fIAuto\(hyaction\(hyregistration\(hyparameter\fR
.sp 9p
.RT
.PP
Defining an \fBauto\(hyaction\(hytype\fR also involves specifying the ASN.1
data\(hytype to which the \fBauto\(hyaction\(hyregistration\(hyparameter\fR
must conform. The data\(hytype of an \fBregistration\(hyparameter\fR is
defined through the
object\(hyidentifier for the \fBauto\(hyaction\(hytype\fR .
.RT
.sp 1P
.LP
6.5.4
\fIAuto\(hyaction\(hytype definition and the AUTO\(hyACTION macro\fR
.sp 9p
.RT
.PP
The definition of an \fBauto\(hyaction\(hytype\fR involves:
.RT
.LP
a)
assigning an object\(hyidentifier to the \fBauto\(hyaction\(hytype\fR ;
.LP
b)
indicating the ASN.1 data\(hytype of the
\fBauto\(hyaction\(hyregistration\(hyparameter\fR .
.PP
The following ASN.1 macro may (but need not) be used to define an \fBauto\(hyaction\(hytype\fR
:
.LP
AUTO\(hyACTION MACRO ::=
.LP
BEGIN
.LP
TYPE NOTATION
::=
Registration
.LP
VALUE NOTATION
::=
value (VALUE OBJECT IDENTIFIER)
.LP
Registration
::=
\*QREGISTRATION PARAMETER IS\*U type
.LP
END
.PP
The correspondence between the parts of the definition, as listed above,
and the various pieces of the notation introduced by the \fBAUTO\(hyACTION\fR
macro, is as follows:
.LP
a)
\fBRegistration\fR : gives the data\(hytype of the registration
parameters association with an auto\(hyaction.
.LP
b)
\fBValue\fR : the \fBobject\(hyidentifier\fR which is used to identify
the auto\(hyaction.
.PP
\fINote\fR \ \(em\ No support is provided in the macro for defining the
interaction (if any) between different registrations of the same (or different)
\fBauto\(hyactions\fR .
.bp
.sp 1P
.LP
6.6
\fIForwarding of messages\fR
.sp 9p
.RT
.PP
The MS\(hyuser makes use of the message\(hysubmission
abstract\(hyoperation and its parameters as defined in \(sc\ 8.2 of
Recommendation\ X.411 to request that a message stored in the MS be explicitly
forwarded to other users.
.PP
The \fBforwarding\(hyrequest parameter\fR is defined using the \fBEXTENSION\fR
macro defined in \(sc\ 9 of Recommendation\ X.411 as follows:
.RT
.LP
forwarding\(hyrequest EXTENSION
.LP
SequenceNumber
.LP
CRITICAL FOR SUBMISSION
.LP
::= 36
.PP
If the \fBsequence\(hynumber\fR supplies does not match that of an entry
into the \fBstored messages information\(hybase\fR , or matches an entry
that is
unsuitable for forwarding, this is reported using the \fBinconsistent\(hyrequest\fR
abstract\(hyerror of \(sc\ 8.2.2.7 of Recommendation\ X.411.
.sp 2P
.LP
\fB7\fR \fBAbstract\(hybind and abstract\(hyunbind operations\fR
.sp 1P
.RT
.sp 1P
.LP
7.1
\fIAbstract\(hybind\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBMS\(hybind abstract\(hybind\(hyoperation\fR binds the
indirect\(hysubmission, retrieval and administration ports of the MS\(hyuser
(consumer) to the MS (supplier). The initiator (of the MS\(hybind) is the
MS\(hyuser, while the responder is the MS itself. MS\(hybind is defined
as follows:
.RT
.LP
MSBind ::= ABSTRACT\(hyBIND
.LP
TO {\|IndirectSubmission[5], retrieval[5],
administration[5]\|}
.LP
BIND
.LP
\ \ ARGUMENT
MSBindArgument
.LP
\ \ RESULT
MSBindResult
.LP
\ \ BIND\(hyERROR
MSBindError
.PP
Only one abstract\(hyassociation may exist at any one time between
the MS and the MS\(hyuser.
.sp 1P
.LP
7.1.1
\fIAbstract\(hybind\(hyargument\fR
.sp 9p
.RT
.PP
The \fBabstract\(hybind\(hyargument\fR parameters are used to identify,
authenticate and set the security\(hycontext for an MS abstract\(hyservice\(hyuser.
They also contain a set of restrictions for entries to be returned as result
of a
Fetch abstract\(hyoperation, and finally, a request to be informed of the
auto\(hyaction\(hytypes, attribute\(hytypes and content\(hytypes supported
by the MS.
.PP
The definition of these parameters is as follows:
.RT
.LP
MSBindArgument ::= SET\|{
.LP
initiator\(hyname
ORAddressAndOrDirectoryName,
.LP
initiator\(hycredentials
[2]\ InitiatorCredentials,
.LP
security\(hycontext
[3]\ IMPLICIT
SecurityContext OPTIONAL,
.LP
fetch\(hyrestrictions
[4]\ Restrictions
OPTIONAL\ \(hy\(hy\ \fIdefault is none\fR \ \(hy\(hy,
.LP
ms\(hyconfiguration\(hyrequest
[5]\ BOOLEAN DEFAULT
FALSE\|}
.LP
1)
\fBInitiator\(hyname\fR (C): This argument contains the name of the
initiator of the association and is supplied by the initiator.
This argument is defined further in \(sc\ 8.1.1.1.1.1 of
Recommendation\ X.411.
.LP
2)
\fBInitiator\(hycredentials\fR (M): This parameter contains the
\fBcredentials\fR of the initiator of the association. It shall be
generated by the initiator of the abstract\(hyassociation.
.LP
The \fBinitiator\(hycredentials\fR may be used by the responder to
authenticate the identity of the initiator
(see\ Recommendation\ X.509).
.LP
If only \fBsimple\(hyauthentication\fR is used, the
\fBinitiator\(hycredentials\fR comprise a simple password.
.LP
If \fBstrong\(hyauthentication\fR is used, the
\fBinitiator\(hycredentials\fR comprise an \fBinitiator\(hybind\(hytoken\fR
, and,
optionally, an \fBinitiator\(hycertificate\fR . The
\fBinitiator\(hybind\(hytoken\fR and \fBinitiator\(hycertificate\fR are defined
further in \(sc\ 8.1.1.1.1.2 of Recommendation\ X.411. The
\fB
initiator\(hycredentials\fR of the MS\(hyuser may differ from the
\fBinitiator\(hycredentials\fR used in the \fBMTS\(hybind\fR as defined in
\(sc\ 8.1.1.1.1.2 of Recommendation\ X.411.
.bp
.LP
3)
\fBSecurity\(hycontext\fR (O): This parameter identifies the
\fBsecurity\(hycontext\fR that the initiator of the
abstract\(hyassociation proposes to operate at. It is generated by
the initiator of the abstract\(hyassociation. The
\fBsecurity\(hycontext\fR is defined further in \(sc\ 8.1.1.1.1.3 of
Recommendation\ X.411.
.LP
The \fBsecurity\(hycontext\fR comprises one or more
\fBsecurity\(hylabels\fR that define the sensitivity of interactions
that may occur between the MS abstract\(hyservice\(hyuser and the
MS\(hyabstract\(hyservice for the duration of the abstrct\(hyassociation,
in line with the \fBsecurity\(hypolicy\fR in force. The
\fBsecurity\(hycontext\fR shall be one that is allowed by the
registered \fBuser\(hysecurity\(hylabels\fR of the
MS\(hyabstract\(hyservice\(hyuser and by the \fBsecurity\(hylabels\fR with the
MS.
.LP
In the absence of this parameter, \fBsecurity\(hycontexts\fR are
not established between the MS\(hyabstract
\(hyservice\(hyuser and the
MS\(hyabstract\(hyservice is at the discretion of the invoker of
the abstract\(hyservice.
.LP
4)
\fBFetch\(hyrestrictions\fR (O): This contains the restrictions on
entries to be returned as result of a fetch abstract\(hyoperation.
The \fBfetch\(hyrestrictions\fR remain set until an
abstract\(hyunbind\(hyoperation is issued.
.LP
In the absence of this argument, the default is that no
\fBfetch\(hyrestrictions\fR need to be performed.
.LP
This argument consists of the following components:
.LP
Restrictions ::= SET\|{
.LP
allowed\(hycontent\(hytypes
[0]\ SET
SIZE (1\|.\|.\|ub\(hycontent\(hytypes) OF OBJECT IDENTIFIER
.LP
allowed\(hycontent\(hytypes
[0]\
OPTIONAL
.LP
\ \ \(hy\(hy\ \fIdefault is no restriction\fR \ \(hy\(hy,
.LP
allowed\(hyEITs
[1]\ MS\(hyEITs
OPTIONAL\ \(hy\(hy\ \fIdefault is no restriction\fR \ \(hy\(hy
.LP
maximum\(hycontent\(hylength
[2]\ ContentLength
OPTIONAL\ \(hy\(hy\ \fIdefault is no restriction\fR \ \(hy\(hy
.LP
a)
\fBAllowed\(hycontent\(hytypes\fR (C): The content\(hytypes that the
MS abstract\(hyservice\(hyuser is prepared to accept as result of a
Fetch abstract\(hyoperation. Any message with a content\(hytype other
than the ones specified will not be returned, but result in an
error, unless the Fetch abstract\(hyoperation has explicitly
overriden the restriction.
.LP
In the absence of this component, the default is that
no fetch\(hyrestrictions on content\(hytypes need to be performed.
.LP
b)
\fBAllowed\(hyEITs\fR (C): The encoded\(hyinformation\(hytypes that the
MS abstract\(hyservice\(hyuser is prepared to accept as result of a
fetch abstract\(hyoperation. If a message contains
encoded\(hyinformation\(hytypes other than the ones specified, a
filtering will take place so that disallowed EIT parts are not
returned along with the text of the message. If the whole
message consists of disallowed EITs, an error will be reported.
No filtering will take place if the fetch abstract\(hyoperation
has explicitly overridden the restriction.
.LP
MS\(hyEITs ::= SET SIZE (1\|.\|.\|ub\(hyencoded\(hyinformation\(hytypes)
OF MS\(hyEIT
.LP
MS\(hyEIT ::= OBJECT IDENTIFIER
.LP
In the absence of this component, the default is that no
\fBfetch\(hyrestrictions\fR on encoded\(hyinformation\(hytypes need to be
performed.
.LP
c)
\fBMaximum\(hycontent\(hylength\fR (C): The maximum content length
that the MS\(hyabstract\(hyservice\(hyuser is prepared to accept as a
result of a fetch abstract\(hyoperation. Any message with a
\fBcontent\(hylength\fR exceeding the one specified will not be
returned, but result in an error, unless the fetch
abstract\(hyoperation has explicitly overridden the restriction.
.LP
In the absence of this component, the default is that
no \fBfetch\(hyrestrictions\fR on \fBcontent\(hylength\fR need to be
performed.
.LP
5)
\fBMS\(hyconfiguration\(hyrequest\fR (C): The
\fBMS\(hyconfiguration\(hyrequest\fR is requested to obtain information
relating to which auto\(hyactions and optional attributes the MS
provides support for.
.LP
In the absence of this component, the default is false
which indicates that no such request is being
made.
.bp
.sp 1P
.LP
7.1.2
\fIAbstract\(hybind\(hyresult\fR
.sp 9p
.RT
.PP
The abstract\(hybind\(hyresult parameters are as follows:
.RT
.LP
MSBindResult ::= SET\|{
.LP
responder\(hycredentials
[2]\ ResponderCredentials,
.LP
available\(hyauto\(hyactions
[3]\ SET
SIZE (1\|.\|.\|ub\(hyauto\(hyactions) OF AutoActionType OPTIONAL,
.LP
available\(hyattribute\(hytypes
[4]\ SET
SIZE (1\|.\|.\|ub\(hyattributes\(hysupported) OF Attribute Type
.LP
available\(hyattribute\(hytypes
[4]\
OPTIONAL,
.LP
alert\(hyindication
[5]\ BOOLEAN DEFAULT FALSE,
.LP
content\(hytypes\(hysupported
[6]\ SET
SIZE (1\|.\|.\|ub\(hycontent\(hytypes) OF OBJECT IDENTIFIER
.LP
content\(hytypes\(hysupported
[6]\
OPTIONAL\|}
.LP
1)
\fBResponder\(hycredentials\fR (M): This parameter contains the
credentials of the responder of the abstract\(hyassociation. It
shall be generated by the responder of the
abstract\(hyassociation.
.LP
The \fBresponder\(hycredentials\fR may be used by the initiator to
authenticate the identity of the responder (see
Recommendation\ X.509).
.LP
If only \fBsimple\(hyauthentication\fR is used, the
\fBresponder\(hycredentials\fR comprise a simple \fBpassword\fR associated
with the responder.
.LP
If \fBstrong\(hyauthentication\fR is used, the \fBresponder\(hycredentials\fR
comprise a \fBresponder\(hybind\(hytoken\fR , and, optionally, a
\fBresponder\(hycertificate\fR , both of which are generated by the responder
of the abstract\(hyassociation. The \fBresponder\(hybind\(hytoken\fR and
\fBresponder\(hycertificate\fR are defined further in \(sc\ 8.1.1.1.2.2 of
Recommendation\ X.411.
.LP
2)
\fBAvailable\(hyauto\(hyactions\fR (C): Specifies the set of all possible
\fBauto\(hyactions\fR that are supported by the MS (not just those requested
by the MS abstract\(hyservice\(hyuser). Only present if an
\fBMS\(hyconfiguration\(hyrequest\fR is made.
.LP
3)
\fBAvailable\(hyattribute\(hytypes\fR (C): Specifies the set of all
optional attributes supported by the MS. Only present if an
\fBMS\(hyconfiguration\(hyrequest\fR is made.
.LP
4)
\fBAlert\(hyindication\fR (C): If true then an \fBalert\fR condition
has occurred since the last successful \fBAlert\(hy\fR \fBindication\fR .
.LP
5)
\fBContent\(hytypes\(hysupported\fR (C): Specifies a set of
object\(hyidentifiers that define the \fBcontent\(hytypes\fR that the MS
has knowledge of. Only present if an \fBMS\(hyconfiguration\(hyrequest\fR
is made.
.sp 1P
.LP
7.1.3
\fIAbstract\(hybind\(hyerrors\fR
.sp 9p
.RT
.PP
There are two possible errors defined by the \fBretrieval port\fR ,
namely \fBauthentication\(hyerror\fR and \fBunacceptable\(hysecurity\(hycontext\fR
.
.PP
The definition of the errors is:
.RT
.LP
MSBindError ::= ENUMERATED\|{
.LP
authentication\(hyerror
(0),
.LP
unacceptable\(hysecurity\(hycontext
(1),
.LP
unable\(hyto\(hyestablish\(hyassociation
(2)}
.LP
1)
\fBAuthentication\(hyerror\fR (C): This error reports that an
abstract\(hyassociation cannot be established because the
initiator's \fBcredentials\fR are not acceptable or are
improperly specified.
.LP
The \fBauthentication\(hyerror\fR has no parameters.
.LP
2)
\fBUnacceptable\(hysecurity\(hycontext\fR (C): This error reports that
the \fBsecurity\(hycontext\fR proposed by the initiator of the
abstract\(hyassociation is unacceptable to the responder.
.LP
The \fBunacceptable\(hysecurity\(hycontext\fR error has no
parameters.
.LP
3)
\fBUnable\(hyto\(hyestablish\(hyassociation\fR (C): This error reports
that the responder has rejected the initiator's attempt to
establish an abstract\(hyassociation.
.LP
The \fBunable\(hyto\(hyestablish\(hyassociation\fR error has no
parameters.
.sp 1P
.LP
7.2
\fIAbstract\(hyunbind\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBMS\(hyunbind abstract\(hyunbind\(hyoperation\fR closes the
abstract\(hyassociation. The issuing of an \fBabstract\(hyunbind\(hyoperation\fR
results in the relaxation of any \fBfetch\(hyrestrictions\fR that were
specified in the
\fBabstract\(hybind operation\fR argument. There is no argument, result,
or error
associated with the \fBabstract\(hyunbind\(hyoperation\fR .
.RT
.LP
MSUnbind ::= ABSTRACT\(hyUNBIND
.LP
FROM {\|indirectSubmission[S], retrieval[S],
administration[S]\|}
.bp
.sp 2P
.LP
\fB8\fR \fBAbstract\(hyoperations\fR
.sp 1P
.RT
.PP
This paragraph defines the following \fBabstract\(hyoperations\fR
available at the retrieval port:
.RT
.LP
a)
summarize;
.LP
b)
list;
.LP
c)
fetch;
.LP
d)
delete;
.LP
e)
register\(hyMS;
.LP
f
)
alert.
.PP
The MS is the MS abstract\(hyservice\(hyprovider of each of these
\fBabstract\(hyoperations\fR . For the formal definition of the retrieval
port, see
\(sc\ 6.2.
.PP
The abstract\(hyoperations may be performed asynchronously subject to the
following conditions. The delete and register\(hyMS abstract\(hyoperations
shall not be performed until all outstanding abstract\(hyoperations have
been completed.
Additionally these abstract\(hyoperations are performed in the order in
which they are invoked and are required to complete prior to any other
abstract\(hyoperations being performed. As a consequence of this and the
fact that the list and fetch abstract\(hyoperations change the status of
a message entry, the results of the
summarize, list and fetch abstract\(hyoperations may be non\(hydeterministic.
.RT
.sp 1P
.LP
8.1
\fICommon\(hydata\(hytypes used in abstract\(hyoperations\fR
.sp 9p
.RT
.PP
This paragraph defines a number of common data\(hytypes which are used
in several of the \fBabstract\(hy operations\fR defined in the remainder
of \(sc\ 8.
Many of the \fBabstract\(hyoperations\fR also make use of entries and attributes
as
defined in \(sc\ 6.3.
.PP
The common data\(hytypes defined in this Recommendation are:
.RT
.LP
a)
range;
.LP
b)
filter;
.LP
c)
selector;
.LP
d)
entry information selection;
.LP
e)
entry information.
.sp 1P
.LP
8.1.1
\fIRange\fR
.sp 9p
.RT
.PP
A \fBrange\fR parameter is used to select a contiguous sequence of
entries from an information\(hybase.
.RT
.LP
Range ::= CHOICE\|{
.LP
sequence\(hynumber\(hyrange
[0]\ NumberRange,
.LP
creation\(hytime\(hyrange
[1]\ TimeRange\|}
.LP
NumberRange ::= SEQUENCE\|{
.LP
from
[0]\ SequenceNumber OPTIONAL \(em \fIomitted means no\fR \fIlower bound\fR
\ \(hy\(hy,
.LP
to
[1]\ SequenceNumber OPTIONAL \(em \fIomitted means no\fR \fIupper bound\fR
\ \(hy\(hy\|}
.LP
TimeRange ::= SEQUENCE\|{
.LP
from
[0]\ CreationTime OPTIONAL \(em \fIomitted means no\fR \fIlower bound\fR
\ \(hy\(hy,
.LP
to
[1]\ CreationTime OPTIONAL \(em \fIomitted means no\fR \fIupper bound\fR
\ \(hy\(hy\|}
.LP
CreationTime ::= UTCTime
.PP
The components of \fBrange\fR have the following meanings:
.LP
1)
\fBSequence\(hynumber\(hyrange\fR (C), and
.LP
2)
\fBCreation\(hytime\(hyrange\fR (C): Both of these parameters identify
the contiguous sequence of entries to be selected. The
\fBsequence\(hynumber\(hyrange\fR is given in terms of \fBsequence\(hynumbers\fR
,
and the \fBcreation\(hytime\(hyrange\fR is given in terms of
\fBcreation\(hytimes\fR . The \fBcreation\(hytime\fR of an entry is the time
at which the MS generated the entry. The sequence numbers of
successive entries are always in ascending order, but several
adjacent entries may have the same \fBcreation time\fR . The
parameters of both \fBnumber\(hyrange\fR and \fBtime\(hyrange\fR have the
following meanings:
.LP
a)
\fBFrom\fR (O): This is the lower bound for the \fBrange\fR .
.LP
In the absence of this component, the default is
\fBno lower bound\fR , and the selection starts with the
earliest message (lowest \fBsequence\(hynumber\fR ) in the
information\(hybase.
.LP
b)
\fBTo\fR (O): This is the upper bound for the \fBrange\fR .
.LP
In the absence of this component, the default is
\fBno upper bound\fR , and the selection finishes with the
latest message (highest \fBsequence\(hynumber\fR ) in the
information\(hybase.
.bp
.sp 2P
.LP
8.1.2
\fIFilters\fR
.sp 1P
.RT
.sp 1P
.LP
8.1.2.1
\fIFilter\fR
.sp 9p
.RT
.PP
A \fBfilter\fR parameter applies a test to a particular entry and is
either satisfied or not by the entry. The \fBfilter\fR is expressed in terms of
assertions about the presence or value of certain attributes of the entry,
and is satisfied if and only if it evaluates to \fBtrue\fR .
.RT
.LP
Filter ::= CHOICE\|{
.LP
item
[0]\ FilterItem,
.LP
and
[1]\ SET SIZE (1\|.\|.\|ub\(hynested\(hyfilters) OF Filter,
.LP
or
[2]\ SET SIZE (1\|.\|.\|ub\(hynested\(hyfilters) OF Filter,
.LP
not
[3]\ Filter\|}
.PP
A \fBfilter\fR is either a \fBfilter\(hyitem\fR , or an expression involving
simpler \fBfilters\fR composed together using the logical operators \fBand\fR
, \fBor\fR ,
and \fBnot\fR .
.PP
Where the \fBfilter\fR is:
.RT
.LP
a)
an \fBitem\fR , it is \fBtrue\fR if and only if the corresponding
\fBfilter\(hyitem\fR is \fBtrue\fR ;
.LP
b)
an \fBand\fR , it is \fBtrue\fR unless any of the \fBfilters\fR in the
\fBSET\fR are \fBfalse\fR .
.LP
\fINote\fR \ \(em\ Thus, if there are no \fBfilters\fR in the \fBSET\fR , the
\fBand\fR evaluates to \fBtrue\fR .
.LP
c)
an \fBor\fR , it is \fBfalse\fR unless any of the \fBfilters\fR in the
\fBSET\fR are \fBtrue\fR ;
.LP
\fINote\fR \ \(em\ Thus, if there are no \fBfilters\fR in the \fBSET\fR , the
\fBor\fR evaluates to \fBfalse\fR .
.LP
d)
a \fBnot\fR , it is \fBtrue\fR if and only if the \fBfilter\fR is
\fBfalse\fR .
.sp 1P
.LP
8.1.2.2
\fIFilter\(hyitem\fR
.sp 9p
.RT
.PP
A \fBfilter\(hyitem\fR is an assertion about the presence or value(s) of
an attribute of a particular type in the entry under test. Each such assertion
is either \fBtrue\fR or \fBfalse\fR .
.RT
.LP
FilterItem ::= CHOICE\|{
.LP
equality
[0]\ AttributeValueAssertion,
.LP
substrings
[1]\ SEQUENCE\|{
.LP
\ \ type
AttributeType,
.LP
\ \ strings
SEQUENCE SIZE (1\|.\|.\|ub\(hyattribute\(hyvalues)
OF CHOICE\|{
.LP
\ \ \ initital
\ \ [0]\ ANY \(hy\(hy\ \fIDEFINED BY type\fR \ \(hy\(hy,
.LP
\ \ \ any
\ \ [1]\ ANY \(hy\(hy\ \fIDEFINED BY type\fR \ \(hy\(hy,
.LP
\ \ \ final
\ \ [2]\ ANY \(hy\(hy\ \fIDEFINED BY type\fR \ \(hy\(hy\|}\|},
.LP
greater\(hyor\(hyequal
[2]\ AttributeValueAssertion,
.LP
less\(hyor\(hyequal
[3]\ AttributeValueAssertion,
.LP
present
[4]\ AttributeType,
.LP
approximate\(hymatch
[5]\ AttributeValueAssertion\|}
.PP
Every filter\(hyitem includes an attribute\(hytype which identifies the
particular attribute concerned.
.PP
Any assertion about the value of such an attribute is only evaluated if
the attribute\(hytype is defined, and the purposed attribute\(hyvalue(s)
are of
the data\(hytype defined for attribute\(hyvalues of that attribute.
.PP
Assertions about the value of an attribute by matching the attribute for
EQUALITY, SUBSTRINGS, and ORDERING, as defined in \(sc\ 6.3.3.4.
.PP
Where the \fBfilter\(hyitem\fR asserts:
.RT
.LP
a)
\fBequality\fR , it is \fBtrue\fR if and only if there is a value of
the attribute which is equal to that asserted;
.LP
b)
\fBsubstrings\fR , it is \fBtrue\fR if and only if there is a value
of the attribute in which the specified \fBsubstrings\fR appear in
the given order. The \fBsubstrings\fR must be non\(hyoverlapping, and
may (but need not) be separated from the ends of the
attribute\(hyvalue and from one another by zero or more \fBstring\fR
elements.
.LP
The first character in \fBinitial\fR , if present, shall match
the first character in the attribute\(hyvalue; the last character
in \fBfinal\fR , if present, shall match the last character in the
attribute\(hyvalue. \fBany\fR , if present, may match any substring in
the attribute\(hyvalue;
.LP
c)
\fBgreater\(hyor\(hyequal\fR , it is \fBtrue\fR if and only if the relative
ordering places the supplied value \fIafter\fR any value of the
attribute;
.bp
.LP
d)
\fBless\(hyor\(hyequal\fR , it is \fBtrue\fR if and only if the relative
ordering places the supplied value \fIbefore\fR any value of the
attribute;
.LP
e)
\fBpresent\fR , it is \fBtrue\fR if and only if such an attribute
is present in the entry;
.LP
f
)
\fBapproximate\(hymatch\fR , it is \fBtrue\fR if and only if there
is a value of the attribute which matches that which is asserted
by some locally\(hydefined approximate matching algorithm
(e.g.\ spelling variations, phonetic match,\ etc.) There are no
specific guidelines for approximate matching in this version of
the Recommendation. If approximate matching is not supported,
this \fBFilterItem\fR should be treated as match for
\fBequality\fR .
.PP
\fINote\fR \ \(em\ If no matching rules are given in the attribute
definition, this means that only the presence of the attribute can be tested
in a \fBfilter\(hyitem\fR .
.sp 1P
.LP
8.1.2.3
\fIAttribute\(hyvalue\(hyassertion\fR
.sp 9p
.RT
.PP
An \fBattribute\(hyvalue\(hyassertion\fR is a proposition, which may be
\fBtrue\fR , \fBfalse\fR , or \fBundefined\fR , concerning the values of
an entry. It involves an attribute\(hytype and an attribute\(hyvalue:
.RT
.LP
AttributeValueAssertion ::= SEQUENCE\|{
.LP
type
AttributeType,
.LP
value
ANY DEFINED BY type\|}
.LP
and is:
.LP
a)
\fBunderfined\fR , if any of the following holds:
.LP
1)
the attribute\(hytype is not present in the entry;
.LP
2)
the definition of the attribute\(hytype cannot be
matched for equality or ordering;
.LP
3)
the attribute\(hyvalue does not conform to the data
type of the attribute\(hyvalues;
.LP
b)
\fBtrue\fR , if the entry contains an attribute of that
attribute\(hytype, one of whose attribute\(hyvalues matches that
attribute\(hyvalue;
.LP
c)
\fBfalse\fR , otherwise.
.sp 1P
.LP
8.1.3
\fISelector\fR
.sp 9p
.RT
.PP
A \fBselector\fR parameter is used to select entries from an
information\(hybase. The selection operates in three stages. Firstly, the total
set of entries in the information\(hybase may be restricted to particular
contiguous set by specifying its range. Secondly, entries from within this
set may be selected by specifying a filter which the selected entry must
satisfy. Thirdly, a limit may be placed on the number of entries thus selected;
in this case, it is those entries with the lowest sequence\(hynumbers which
are
selected.
.RT
.LP
Selector ::= SET\|{
.LP
child\(hyentries
[0]\ BOOLEAN DEFAULT FALSE,
.LP
range
[1]\ Range OPTIONAL \(hy\(hy\ \fIdefault is\fR \fIunbounded\fR \ \(hy\(hy,
.LP
filter
[2]\ Filter OPTIONAL \(hy\(hy\ \fIdefault is all\fR \fIentries within the
specified range\fR \ \(hy\(hy,
.LP
limit
[3]\ INTEGER (1\|.\|.\|ub\(hymessages) OPTIONAL,
.LP
override
[4]\ OverrideRestrictions OPTIONAL
\(hy\(hy\ \fIdefault is that any fetch\(hyrestrictions in force\fR
.LP
override
[4]\
\fIdo apply\ \fR \(hy\(hy\|}
.PP
The components of \fBselector\fR have the following meanings:
.LP
1)
\fBChild\(hyentries\fR (O): If \fBfalse\fR , only main\(hyentries are
considered for selection. If \fBtrue\fR , both main\(hyentries and
child\(hyentries are considered for selection.
.LP
In the absence of this component, the default is
\fIonly main\(hyentries are considered\fR .
.LP
2)
\fBRange\fR (O): The abstract\(hysyntax\(hynotation of \fBrange\fR is given
in \(sc\ 8.1.1.
.LP
In the absence of this component, the default is
\fIunbounded\fR .
.LP
3)
\fBFilter\fR (O): The abstract\(hysyntax\(hynotation of \fBfilter\fR is
given in \(sc\ 8.1.2.
.LP
In the absence of this component, the default is
\fIall entries within the specified range\fR .
.LP
4)
\fBLimit\fR (O): This allows the specification of an upper limit
on how many entries shall be selected.
.LP
In the absence of this component, all of the selected
entries will be returned.
.LP
\fINote\fR \ \(em\ The primary role of the limit is to protect against
huge results from an abstract\(hyoperation as a consequence of
badly formulated selections. It can also be used to give back an
exact number of information\(hysets to fit a particular
output\(hydevice.
.bp
.LP
5)
\fBOverride\fR (O): If an override of any of the
\fBfetch\(hyrestrictions\fR is required, the corresponding component(s)
of \fBoverride\(hyrestrictions\fR must be present.
.LP
OverrideRestrictions ::= BIT STRING\|{
.LP
overrideContentTypesRestriction
(0),
.LP
overrideEITsRestriction
(1),
.LP
overrideContentLengthRestriction
(2)\|} (SIZE
(1\|.\|.\|ub\(hyinformation\(hybases))
.LP
The bits of \fBoverride\(hyrestrictions\fR have the following meaning:
.LP
a)
\fBOverride\(hycontent\(hytypes\(hyrestriction\fR (M): This bit must \fR
be set to 1 if the \fBcontent\(hytypes\(hyrestriction\fR shall be
overridden.
.LP
If this bit is set to 0, the \fBcontent\(hytypes\(hyrestrictions\fR as
specified in the abstract\(hybind\(hyoperation will be applied.
.LP
b)
\fBOverride\(hyEITs\(hyrestriction\fR (M): This bit must be set to 1
if the \fBEITs\(hyrestriction\fR shall be overridden.
.LP
If this bit is set to 0, the \fBEITs\(hyrestrictions\fR as
specified in the abstract\(hybind\(hyoperation will be applied.
.LP
c)
\fBOverride\(hycontent\(hylength\(hyrestriction\fR (M): This bit must
be set to 1 if the \fBcontent\(hylength\(hyrestriction\fR shall be
overridden.
.LP
If this bit is set to 0, the \fBcontent\(hylength\(hyrestrictions\fR
as specified in the abstract\(hybind\(hyoperation will be applied.
.LP
In the absence of \fBoverride\(hyrestrictions\fR , the default is that all
the \fBfetch\(hyrestrictions\fR as specified in the abstract\(hybind\(hyoperation
will be applied.
.sp 1P
.LP
8.1.4
\fIEntry\(hyinformation\(hyselection\fR
.sp 9p
.RT
.PP
An \fBentry\(hyinformation\(hyselection\fR parameter indicates what
information from an entry is being requested.
.RT
.LP
EntryInformationSelection ::= SET SIZE (0\|.\|.\|ub\(hyper\(hyentry) OF
AttributeSelection
.PP
An empty set indicates that information about the entry itself,
rather than the attributes of entry, is being requested.
.LP
AttributeSelection ::= SET\|{
.LP
type
AttributeType,
.LP
from
[0]\ INTEGER (1\|.\|.\|ub\(hyattribute\(hyvalues)
OPTIONAL\ \(hy\(hy\ \fIused if type is multi valued\fR \ \(hy\(hy,
.LP
count
[1]\ INTEGER (1\|.\|.\|ub\(hyattribute\(hyvalues)
OPTIONAL\ \(hy\(hy\ \fIused if type is multi valued\fR \ \(hy\(hy\|}
.PP
The components of \fBattribute\(hyselection\fR have the following
meaning:
.LP
1)
\fBType\fR (M): This indicates the attribute\(hytype of the
attribute.
.LP
2)
\fBFrom\fR (O): When an attribute is multi\(hyvalued, this integer gives
the relative position of the first value to be returned. If it
specifies a value beyond those present in the attribute, no values
are returned. This component may only be present if the attribute\(hytype
is multi\(hyvalued. If it is omitted, values starting at the first value
are returned.
.LP
3)
\fBCount\fR (O): When an attribute is multi\(hyvalued, this integer gives
the number of values to be returned. If there are less than \fBcount\fR
values present in the attribute, all values are returned. This component
may only be present if the attribute\(hytype is multi\(hyvalued. If it is
omitted, there is no limit as to how many values are returned.
.sp 1P
.LP
8.1.5
\fIEntry\(hyinformation\fR
.sp 9p
.RT
.PP
An \fBentry\(hyinformation\fR parameter conveys selected information from
an entry.
.RT
.LP
EntryInformation ::= SEQUENCE\|{
.LP
sequence\(hynumber
SequenceNumber,
.LP
attributes
SET SIZE (1\|.\|.\|ub\(hyper\(hyentry) OF
Attribute OPTIONAL\|}
.PP
The components of \fBentry\(hyinformation\fR have the following
meanings:
.LP
1)
\fBSequence\(hynumber\fR (M): The sequence\(hynumber identifying
the entry. See \(sc\ 6.3.2.2.
.LP
2)
\fBAttributes\fR (O): The set of selected attributes from the
entry. Where explicitly requested by a partial\(hyattribute\(hyrequest, a
selected attribute that is defined to be multi\(hyvalued may contain
a subset of all the attribute\(hyvalues in the attribute as stored in
the entry. This parameter is absent if information from the selected
messages is not requested, for example, when the MS\(hyabstract\(hyservice\(hyuser
wants only the sequence\(hynumbers of the selected messages.
.bp
.sp 1P
.LP
8.2
\fISummarize abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBSummarize abstract\(hyoperation\fR returns summary counts of
selected entries in an information\(hybase. In addition to these summaries, a
count of the entries selected, and their lowest and highest sequence\(hynumbers
are also returned. Zero or more individual summaries may be requested.
.PP
The \fBsummarize abstract\(hyoperations\fR will only be successful when
the information\(hybase permits access according to the security\(hycontext
and the
enforced security\(hypolicy.
.PP
The attributes that may be used for summaries are restricted. For the general\(hyattributes
in the stored\(hymessages information\(hybase, the restrictions
are given in Table\ 1/X.413.
.RT
.LP
Summarize ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
SummarizeArgument
.LP
RESULT
SummarizeResult
.LP
ERRORS\|{
.LP
\ \ AttributeError,
.LP
\ \ InvalidParametersError,
.LP
\ \ RangeError,
.LP
\ \ SecurityError,
.LP
\ \ SequenceNumberError,
.LP
\ \ ServiceError\|}
.PP
\fINote\fR \ \(em\ An example of the summarize abstract\(hyoperation is
given in Annex\ F.
.sp 1P
.LP
8.2.1
\fISummarize\(hyargument\fR
.sp 9p
.RT
.LP
SummarizeArgument ::= SET\|{
.LP
information\(hybase\(hytype
[0]\ InformationBase
DEFAULT stored\(hymessages,
.LP
selector
[1]\ Selector,
.LP
summary\(hyrequests
[2]\ SEQUENCE SIZE
(1\|.\|.\|ub\(hysummaries) OF AttributeType OPTIONAL
.LP
\ \ \(hy\(hy\ \fIabsent if no summaries are requested\fR \ \(hy\(hy\|}
.PP
The components of \fBsummarize\(hyargument\fR have the following
meanings:
.LP
1)
\fBInformation\(hybase\(hytype\fR (O): This specifies which
\fBinformation\(hybase\fR is addressed by the abstract\(hyoperation.
See\ \(sc\ 6.3.1.
.LP
In the absence of the \fBinformation\(hybase\(hytype\fR component, the
default is stored\(hymessages.
.LP
2)
\fBSelector\fR (M): This is a set of selection criteria to
determine which entries shall be summarized.
See\ \(sc\ 8.1.3.
.LP
3)
\fBSummary\(hyrequests\fR (O): This is the sequence of
attribute\(hytypes for which summaries are requested. This
parameter is only present if a summary is requested.
.sp 1P
.LP
8.2.2
\fISummarize\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the \fBsummarize\(hyresult\fR will be
returned.
.RT
.LP
SummarizeResult ::= SET\|{
.LP
next
[0]\ SequenceNumber OPTIONAL,
.LP
count
[1]\ INTEGER (0\|.\|.\|ub\(hymessages)\|}\ \(hy\(hy\ \fIof the\fR
\fIentries selected\fR \ \(hy\(hy,
.LP
span
[2]\ Span OPTIONAL\ \(hy\(hy\ \fIof the entries\fR \fIselected, omitted
if count is zero\fR \ \(hy\(hy,
.LP
summaries
[3]\ Sequence SIZE (1\|.\|.\|ub\(hysummaries) OF
Summary OPTIONAL)
.PP
The components of \fBsummarize\(hyresult\fR have the following
meanings:
.LP
1)
\fBNext\fR (C): This is returned in the case where the number of
entries selected would have been greater if it were not for
the limit specified in the selector. The component contains the
sequence\(hynumber for the next entry that would have been
selected.
.LP
2)
\fBCount\fR (M): This is an integer giving the count of entries
that matched the selection criteria.
.LP
3)
\fBSpan\fR (C): This contains the lowest and highest
sequence\(hynumbers of the entries that matched the selection
criteria. It is absent if there are no such entries.
.LP
Span ::= SEQUENCE\|{
.LP
lowest
[0]\ SequenceNumber,
.LP
highest
[1]\ SequenceNumber\|}
.bp
.LP
The components of \fBspan\fR have the following meanings:
.LP
a)
\fBLowest\fR (M): This is the starting\(hypoint for the
\fBspan\fR , given as a sequence\(hynumber (see \(sc\ 6.3.2.2).
.LP
b)
\fBHighest\fR (M): This is the end\(hypoint for the \fBspan\fR given
as a sequence\(hynumber (see \(sc\ 6.3.2.2).
.LP
4)
\fBSummaries\fR (C): One \fBsummary\fR is returned for each
\fBsummary\(hyrequest\fR . The \fBsummaries\fR are returned in the order
that they were requested.
.LP
Summary ::= SET\|{
.LP
absent
[0]\ INTEGER
(1\|.\|.\|ub\(hymessages) OPTIONAL\ \(hy\(hy\ \fIcount of entries\fR \fIwhere
the attribute is\fR
.LP
[0]\
\fIabsent\fR \ \(hy\(hy,
.LP
present
[1]\ SET SIZE (1\|.\|.\|ub\(hyattribute\(hyvalues) OF
\(hy\(hy\ \fIone for each attribute value present\fR \ \(hy\(hy
.LP
SEQUENCE\|{
.LP
\ \ type
AttributeType,
.LP
\ \ value
ANY DEFINED BY type,
.LP
\ \ count
INTEGER (1\|.\|.\|ub\(hymessages)\|}
OPTIONAL\|}
.LP
The components of \fBsummary\fR have the following meanings:
.LP
a)
\fBAbsent\fR (C): A count of the entries that do not contain an
attribute of the attribute\(hytype specified in the request.
It is omitted if there are no such entries.
.LP
b)
\fBPresent\fR (C): A summary of the entries that contain an
attribute of the attribute\(hytype specified, broken down by the
attribute\(hyvalues actually present. It is omitted if there are no
such entries.
.LP
The components of \fBpresent\fR have the following meanings:
.LP
i)
\fBType\fR (M): The type of the attribute.
.LP
ii)
\fBValue\fR (M): The attribute\(hyvalue for which the count
is given.
.LP
iii)
\fBCount\fR (M): A count of entries with this
attribute\(hyvalue.
.sp 1P
.LP
8.2.3
\fISummarize abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in \(sc\ 9.
.RT
.sp 1P
.LP
8.3
\fIList abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBlist\(hyabstract\(hyoperation\fR is used to search a selected
information\(hybase for entries of interest and to return selected information
from those entries.
.PP
The \fBlist\(hyabstract\(hyoperation\fR will only be successful when the
information\(hybase permits access according to the security\(hycontext and the
enforced security policy.
.PP
The information that may be selected for entries in an
information\(hybase may be restricted. For the general\(hyattributes in the
stored\(hymessages information\(hybase, the restrictions are given in
Table\ 1/X.413.
.RT
.LP
List ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
ListArgument
.LP
RESULT
ListResult
.LP
ERRORS\|{
.LP
\ \ AttributeError,
.LP
\ \ InvalidParametersError,
.LP
\ \ RangeError,
.LP
\ \ SecurityError,
.LP
\ \ SequenceNumberError,
.LP
\ \ ServiceError\|}
.sp 1P
.LP
8.3.1
\fIList\(hyargument\fR
.sp 9p
.RT
.LP
ListArgument ::= SET\|{
.LP
Information\(hybase\(hytype
[0]\ InformationBase
DEFAULT stored\(hymessages,
.LP
selector
[1]\ Selector,
.LP
requested\(hyattributes
[3]\ EntryInformationSelection
OPTIONAL\|}
.bp
.PP
The components of \fBlist\(hyargument\fR have the following
meanings:
.LP
1)
\fBInformation\(hybase\(hytype\fR (O): This specifies which
information\(hybase is addressed by the abstract\(hy
operation.
See \(sc\ 6.3.1.
.LP
In the absence of the \fBinformation\(hybase\(hytype\fR component,
the default is stored\(hymessages.
.LP
2)
\fBSelector\fR (M): This is a set of selection criteria to
determine which entries shall be returned. See \(sc\ 8.1.3.
.LP
3)
\fBRequested\(hyattributes\fR (O): This indicates what information
from the selected entries is to be returned in the result.
See \(sc\ 8.1.4.
.LP
If this parameter is absent, the registered set of
\fBlist\(hyattribute\(hydefaults\fR is used. See \(sc\ 8.6.1 for more
information on these defaults.
.sp 1P
.LP
8.3.2
\fIList\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the list\(hyresult will be returned.
.RT
.LP
ListResult ::= SET\|{
.LP
next
[0]\ SequenceNumber OPTIONAL,
.LP
requested
[1]\ SEQUENCE SIZE (1\|.\|.\|ub\(hymessages)
OF EntryInformation OPTIONAL\ \(hy\(hy\ \fIomitted\fR
.LP
requested
[1]\
\fIif none found\fR \ \(hy\(hy\|}
.PP
The components of \fBlist\(hyresult\fR have the following meanings:
.LP
1)
\fBNext\fR (C): This is returned in the case where the number
of entries selected would have been greater if it were not for
the limit specified in the selector. The component contains the
sequence\(hynumber for the next entry that would have been
selected.
.LP
2)
\fBRequested\fR (C): This conveys the requested
entry\(hyinformation (see \(sc\ 8.1.5) from each selected entry (one or
more), in ascending order of sequence\(hynumber. It is not present
in the case that a search was performed and no entry was
selected.
.sp 1P
.LP
8.3.3
\fIList abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in \(sc\ 9.
.RT
.sp 1P
.LP
8.4
\fIFetch abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBfetch\(hyabstract\(hyoperation\fR is used to return selected
information from a specific entry in an information\(hybase. Alternatively,
it is used to return selected information from the first entry from among
several
entries of interest; in this case the sequence\(hynumbers of the other selected
entries are also returned. The \fBfetch\(hyabstract\(hyoperation\fR will
only be
successful when information\(hybases permitted by the security\(hycontext
and the
security\(hypolicy in force are requested.
.PP
Information from an entry can be fetched several times, until the
entry is explicitly deleted using the delete abstract\(hyoperation.
.RT
.LP
Fetch ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
FetchArgument
.LP
RESULT
FetchResult
.LP
ERRORS\|{
.LP
\ \ AttributeError,
.LP
\ \ FetchRestrictionError,
.LP
\ \ InvalidParametersError,
.LP
\ \ RangeError,
.LP
\ \ SecurityError,
.LP
\ \ SequenceNumberError,
.LP
\ \ ServiceError\|}
.sp 1P
.LP
8.4.1
\fIFetch\(hyargument\fR
.sp 9p
.RT
.LP
FetchArgument ::= SET\|{
.LP
information\(hybase\(hytype
[0]\ InformationBase
DEFAULT stored\(hymessages,
.LP
item
\ \ CHOICE\|{
.LP
\ \ search
\ \ \ \ [1]\ Selector,
.LP
\ \ precise
\ \ \ \ [2]\ SequenceNumber\|},
.LP
requested\(hyattributes
[3]\ EntryInformationSelection
OPTIONAL\|}
.bp
.PP
The components of \fBfetch\(hyargument\fR have the following
meanings:
.LP
1)
\fBInformation\(hybase\(hytype\fR (O): This specifies which
information\(hybase is addressed by the abstract\(hyoperation. See
\(sc\ 6.3.1.
.LP
In the absence of the information\(hybase\(hytype component, the
default is stored\(hymessages.
.LP
2)
\fBItem\fR (M): One of the components described below must be
specified in order to determine which entry to fetch:
.LP
a)
\fBSearch\fR (C): This is a selector specifying a set of
entries of which the one with the lowest sequence\(hynumber
is the entry to be fetched. See \(sc\ 8.1.3.
.LP
b)
\fBPrecise\fR (C): This is the sequence\(hynumber of the
entry to be fetched. See \(sc\ 6.3.2.2.
.LP
3)
\fBRequested\(hyattributes\fR (O): This indicates what information
from the selected entry is to be returned in the result (see
\(sc\ 8.1.4).
.LP
If this parameter is absent, the registered set of
\fBfetch\(hyattribute\(hydefaults\fR is used. See \(sc\ 8.6.1 for more
information on these defaults.
.sp 1P
.LP
8.4.2
\fIFetch\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the \fBfetch\(hyresult\fR will be
returned.
.RT
.LP
FetchResult ::= SET\|{
.LP
entry\(hyinformation
[0]\ EntryInformation
OPTIONAL\ \(hy\(hy\ \fIif an entry was selected\fR \ \(hy\(hy,
.LP
list
[1]\ SEQUENCE SIZE (1\|.\|.\|ub\(hymessages)
OF SequenceNumber
.LP
list
[1]\
OPTIONAL,
.LP
next
[2]\ SequenceNumber OPTIONAL\|}
.PP
The components of \fBfetch\(hyresult\fR have the following meanings:
.LP
1)
\fBEntry\(hyinformation\fR (C): This is a set of attributes from one
entry as requested in the argument. See \(sc\ 8.1.5. It is not
present in the case that a search was performed and no entry
was selected.
.LP
2)
\fBList\fR (C): This is returned in the case that a search was
performed and more than one entry was found that matched the
search selector. The list gives the sequence numbers, in
ascending order, of these further entries.
.LP
3)
\fBNext\fR (C): This is returned in the case where the number
of entries selected would have been greater if it were not for
the limit specified in the selector. The component contains
the sequence\(hynumber for the next entry that would have been
selected.
.sp 1P
.LP
8.4.3
\fIFetch abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in \(sc\ 9.
.RT
.sp 1P
.LP
8.5
\fIDelete abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBdelete abstract\(hyoperation\fR is used to delete selected entries
from an information\(hybase. A main\(hyentry and all its dependent child\(hyentries
may only be deleted together. This is achieved by specifying just the main\(hyentry
as an argument. The delete abstract\(hyoperation will only be successful
when
operating on those information\(hybases permitted by the security\(hycontext
and the security\(hypolicy in force.
.PP
For specific information\(hybases, there may be restrictions on which
entries may be deleted. In addition, content specific actions may be taken
as defined in the corresponding Recommendation which defines the content\(hytype.
For the stored\(hymessages, no entry may be deleted if its entry\(hystatus
(see \(sc\ 6.4) is \*Qnew\*U.
.RT
.LP
Delete ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
DeleteArgument
.LP
RESULT
DeleteResult
.LP
ERRORS\|{
.LP
\ \ DeleteError,
.LP
\ \ InvalidParametersError,
.LP
\ \ RangeError,
.LP
\ \ SecurityError,
.LP
\ \ SequenceNumberError,
.LP
\ \ ServiceError\|}
.bp
.sp 1P
.LP
8.5.1
\fIDelete\(hyargument\fR
.sp 9p
.RT
.LP
DeleteArgument ::= SET\|{
.LP
information\(hybase\(hytype
[0]\ InformationBase
DEFAULT stored\(hymessages,
.LP
items
\ \ CHOICE\|{
.LP
\ \ selector
\ \ \ \ [1]\ Selector
.LP
\ \ sequence\(hynumbers
\ \ \ \ [2]\ SET SIZE
(1\|.\|.\|ub\(hymessages) OF SequenceNumber\|}\|}
.PP
The components of \fBdelete\(hyargument\fR have the following
meanings:
.LP
1)
\fBInformation\(hybase\(hytype\fR (O): This specifies which
information\(hybase is addressed by the abstract\(hyoperation. See
\(sc\ 6.3.1.
.LP
In the absence of the \fBinformation\(hybase\(hytype\fR component,
the default is stored\(hymessages.
.LP
2)
\fBItems\fR (M): One of the components described below must
be specified in order to determine which entries to delete.
.LP
a)
\fBSelector\fR (C): See \(sc 8.1.3.
.LP
b)
\fBSequence\(hynumbers\fR (C): An unordered list of
\fBsequence\(hynumbers\fR . See \(sc\ 6.3.2.2.
.sp 1P
.LP
8.5.2
\fIDelete\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the \fBdelete\(hyresult\fR will be returned.
There are no parameters.
.RT
.LP
DeleteResult ::= NULL
.sp 1P
.LP
8.5.3
\fIDelete abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in \(sc\ 9.
.RT
.sp 1P
.LP
8.6
\fIRegister\(hyMS abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The Register\(hyMS abstract\(hyoperation is used to register or
deregister various information with the MS:
.RT
.LP
a)
auto\(hyactions;
.LP
b)
default list of attribute\(hytypes;
.LP
c)
new credentials;
.LP
d)
new set of user\(hysecurity labels.
.LP
Register\(hyMS ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
Register\(hyMSArgument
.LP
RESULT
Register\(hyMSResult
.LP
ERRORS\|{
.LP
\ \ AtrributeError,
.LP
\ \ AutoActionRequestError,
.LP
\ \ InvalidParametersError,
.LP
\ \ SecurityError,
.LP
\ \ ServiceError\|}
.sp 1P
.LP
8.6.1
\fIRegister\(hyMS\(hyargument\fR
.sp 9p
.RT
.LP
Register\(hyMS Arguments := SET\|{
.LP
auto\(hyaction\(hyregistrations
[0]\ SET SIZE
(1\|.\|.\|ub\(hyauto\(hyregistrations) OF AutoActionRegistra\(hy
.LP
auto\(hyaction\(hyregistrations
[0]\
tion OPTIONAL,
.LP
auto\(hyaction\(hyderegistrations
[1]\ SET
SIZE (1\|.\|.\|ub\(hyauto\(hyregistrations) OF AutoActionDere\(hy
.LP
auto\(hyaction\(hyderegistrations
[1]\
gistration OPTIONAL,
.LP
list\(hyattribute\(hydefaults
[2]\ SET SIZE
(1\|.\|.\|ub\(hydefault\(hyregistrations) OF Attribute Type
.LP
list\(hyattribute\(hydefaults
[2]\
OPTIONAL,
.LP
fetch\(hyattribute\(hydefaults
[3]\ SET SIZE
(1\|.\|.\|ub\(hydefault\(hyregistrations) OF Attribute Type
.LP
fetch\(hyattribute\(hydefaults
[3]\
OPTIONAL,
.LP
change\(hycredentials
[4]\ SEQUENCE\|{
.LP
\ \ old\(hycredentials
\ \ [0]\ IMPLICIT Credentials,
.LP
\ \ new\(hycredentials
\ \ [1]\ IMPLICIT Credentials\|} OPTIONAL
.LP
\ \ \ \(hy\(hy\ \fIsame CHOICE as for old\(hycredentials\fR \ \(hy\(hy,
.LP
user\(hysecurity\(hylabels
[5]\ SET SIZE
(1\|.\|.\|ub\(hylabels\(hyand\(hyredirections) OF SecurityLabel
.LP
user\(hysecurity\(hylabels
[5]\
OPTIONAL\|}
.bp
.LP
.PP
The components of register\(hyMS\(hyargument have the following
meanings:
.RT
.LP
1)
\fBAuto\(hyaction\(hyregistrations\fR (O): This is a set of
\fBauto\(hyaction\(hyregistration\fR (see\ \(sc\ 6.5.1), one for each auto\(hyaction
to be
registered. The new \fBauto\(hyaction\(hyregistration\(hyparameter\fR supersedes
any
previously registered auto\(hyaction (if any) with that \fBregistration\(hyidentifier\fR
and \fBauto\(hyaction\(hytype\fR .
.LP
In the absence of \fBauto\(hyaction\(hyregistrations\fR , the default
is that no new auto\(hyactions are registered.
.LP
2)
\fBAuto\(hyaction\(hyderegistrations\fR (O): This is a set of
\fBauto\(hyaction\(hyderegistration\fR , one for each auto\(hyaction to
be deregistered. Any auto\(hyaction with \fBregistration\(hyidentifier\fR
and \fBauto\(hyaction\(hytype\fR matching
those in an \fBauto\(hyaction\(hyderegistration\fR is deregistered.
.LP
AutoActionDeregistration ::= AutoActionRegistration
.LP
(WITH COMPONENTS {\|.\|.\|.\|, registration\(hyparameter
ABSENT\|}\|)
.LP
In the absence of \fBauto\(hyaction\(hyderegistrations\fR , the default
is that no registered auto\(hyactions are deregistered.
.LP
3)
\fBList\(hyattribute\(hydefaults\fR (O): This specifies a default set
of attribute\(hytypes to indicate which attributes should be returned for
any
subsequent list or alert abstract\(hyoperation if the entry\(hyinformation\(hyselection
argument is absent.
.LP
In the absence of \fBlist\(hyattribute\(hydefaults\fR , the default is
that there is no change to the registered default (if any). The
\fBlist\(hyattribute\(hydefaults\fR are the empty set until explicitly
changed by the
MS\(hyuser via the register\(hyMS abstract\(hyoperation.
.LP
4)
\fBFetch\(hyattribute\(hydefaults\fR (O): This specifies a default set
of attribute\(hytypes to indicate which attributes should be returned for
any
subsequent fetch abstract\(hyoperation if the entry\(hyinformation\(hyselection
argument is absent.
.LP
In the absence of \fBfetch\(hyattribute\(hydefaults\fR , the default
is that there is no change to the registered default (if any). The
\fBfetch\(hyattribute\(hydefaults\fR are the empty set until explicitly
changed by the
MS\(hyuser via the register\(hyMS abstract\(hyoperation.
.LP
5)
\fBChange\(hycredentials\fR (O): The old and new credentials if a \fBchange\(hycredentials\fR
is requested.
.LP
The \fBold\(hycredentials\fR are the end user's current
credentials, and the \fBnew\(hycredentials\fR are the credentials the end
user would like to change to.
.LP
In the absence of this argument, the default is that
previously registered credentials remain unchanged.
.LP
The credentials of the MS\(hyuser may differ from the
\fBinitiator\(hycredentials\fR detailed in\ \(sc\ 8.1.1.1.1.2 of Recommendation\
X.411.
.LP
6)
\fBUser\(hysecurity\(hylabels\fR (O): This contains the
\fBsecurity\(hylabel(s)\fR of the MS abstract\(hyservice\(hyuser, if they
are to be changed. It may be generated by the MS abstract\(hyservice\(hyuser.
.LP
In the absence of this argument, the \fBuser\(hysecurity\(hylabels\fR
remain unchanged.
.LP
Note that some \fBsecurity\(hypolicies\fR may only permit the
\fBuser\(hysecurity\(hylabels\fR to be changed in this way if a secure
link is employed. Other local means of changing the \fBuser\(hysecurity\(hylabels\fR
in a secure manner may be provided. \fBUser\(hysecurity\(hylabels\fR is
defined in\ \(sc\ 8.4.1.1.1.7 of
Recommendation\ X.411.
.LP
\fR
\fBSecurity\(hylabel\fR is defined in\ \(sc\ 9 of
Recommendation\ X.411.
.sp 1P
.LP
8.6.2
\fIRegister\(hyMS\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the register\(hyMS\(hyresult will be
returned. There are no parameters.
.RT
.LP
Register\(hyMSResult ::= NULL
.sp 1P
.LP
8.6.3
\fIRegister\(hyMS abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in\ \(sc\ 9.
.bp
.RT
.sp 1P
.LP
8.7
\fIAlert abstract\(hyoperation\fR
.sp 9p
.RT
.PP
The \fBAlert abstract\(hyoperation\fR enables the MS
abstract\(hyservice\(hyprovider to immediately inform the MS abstract\(hyservice\(hyuser
of a new entry having been entered into the MS, whose attributes match
the
selection criteria of one of the \fBauto\(hyalert\(hyregistrations\fR (see\
\(sc\ 12.2)
previously supplied using a Register\(hyMS abstract\(hyoperation (see\
\(sc\ 8.6).
.PP
The \fBAlert abstract\(hyoperation\fR may be invoked during an existing
abstract\(hyassociation initiated by the UA, and only as a result of new
entries created after the establishment of the abstract\(hyassociation.
.PP
Entries matching the selection criteria which have been created
between abstract\(hyassociations will be indicated in the result of the next
abstract\(hybind\(hyoperation for the abstract\(hyassociation. No \fBalert
abstract\(hyoperation\fR will be invoked for these entries. See\ \(sc\ 7.
.PP
The \fBalert abstract\(hyoperation\fR will only be successful when the
information\(hybase permits access according to the security\(hycontext and the
enforced security\(hypolicy.
.RT
.LP
Alert ::= ABSTRACT\(hyOPERATION
.LP
ARGUMENT
AlertArgument
.LP
RESULT
AlertResult
.LP
ERRORS\|{
.LP
\ \ SecurityError\|}
.sp 1P
.LP
8.7.1
\fIAlert\(hyargument\fR
.sp 9p
.RT
.LP
AlertArgument ::= SET\|{
.LP
alert\(hyregistration\(hyidentifier
[0]\ INTEGER
(1\|.\|.\|ub\(hyauto\(hyactions),
.LP
new\(hyentry
[2]\ EntryInformation OPTIONAL\|}
.PP
The components of the \fBalert\(hyargument\fR have the following
meanings:
.LP
1)
\fBAlert\(hyregistration\(hyidentifier\fR (M): Identifies which of
the \fBauto\(hyalert\(hyregistrations\fR resulted in \fBthe\fR alert (see\
\(sc\(sc\ 6.4 and\ 12.2).
.LP
2)
\fBNew\(hyentry \fR (O): This conveys the information from the new entry
which was requested in the \fBauto\(hyalert\(hyregistration\(hyparameter\fR
(see\ \(sc\ 12.2). It is absent when the MS abstract\(hyservice\(hyuser
did not specify an \fBauto\(hyalert\(hyregistration\(hyparameter\fR .
.sp 1P
.LP
8.7.2
\fIAlert\(hyresult\fR
.sp 9p
.RT
.PP
Should the request succeed, the alert\(hyresult will be returned.
.RT
.LP
\fR \fB
AlertResult ::= NULL\fR
.sp 1P
.LP
8.7.3
\fIAlert abstract\(hyerrors\fR
.sp 9p
.RT
.PP
Should the request fail, one of the listed abstract\(hyerrors will be reported.
The circumstances under which the particular abstract\(hyerrors will be
reported are defined in\ \(sc\ 9.
.RT
.sp 2P
.LP
\fB9\fR \fBAbstract\(hyerrors\fR
.sp 1P
.RT
.PP
This paragraph defines the following abstract\(hyerrors associated
with using the abstract\(hyoperations at the retrieval port:
.RT
.LP
a)
AttributeError;
.LP
b)
AutoActionRequestError;
.LP
c)
DeleteError;
.LP
d)
FetchRestrictionError;
.LP
e)
InvalidParametersError;
.LP
f
)
RangeError;
.LP
g)
SecurityError;
.LP
h)
SequenceNumberError;
.LP
i)
ServiceError;
.sp 1P
.LP
9.1
\fIError precedence\fR
.sp 9p
.RT
.PP
The performer of an abstract\(hyoperation is not required to continue processing
the message beyond the point at which an error has been detected.
This allows an implementation to choose whether to continue the processing
of errors.
.bp
.PP
\fINote\fR \ \(em\ An implication of this rule is that the first error
encountered may differ for repeated instances of the same abstract\(hyoperation,
as there is not necessarily a specific logical order in which to process
it.
.RT
.sp 1P
.LP
9.2
\fIAttribute\(hyerror\fR
.sp 9p
.RT
.PP
An \fBattribute\(hyerror\fR reports an attribute related problem.
.RT
.LP
AttributeError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problems\ [0]\ SET SIZE (1\|.\|.\|ub\(hyper\(hyentry) OF SET\|{
.LP
\ \ \ \ problem
[0]\ AttributeProblem,
.LP
\ \ \ \ type
[1]\ AttributeType,
.LP
\ \ \ \ value
[2]\ ANY DEFINED BY type OPTIONAL\|}\|}
.LP
AttributeProblem ::= INTEGER\|{
.LP
invalid\(hyattribute\(hyvalue
(0),
.LP
unavailable\(hyattribute\(hytype
(1),
.LP
inappropriate\(hymatching
(2),
.LP
attribute\(hytype\(hynot\(hysubscribed
(3),
.LP
inappropriate\(hyfor\(hyoperation
(4)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems \fR (M): The particular problems encountered. Any
numbers of individual problems may be indicated, each problem being accompanied
by an indication of the attribute\(hytype, and, if necessary to avoid ambiguity,
the value which caused the problem:
.LP
a)
\fBInvalid\(hyattribute\(hyvalue \fR (C): A purported
attribute\(hyvalue specified as an argument of the abstract\(hyoperation
does not
conform to the data\(hytype defined for the attribute\(hytype concerned.
.LP
b)
\fBUnavailable\(hyattribute\(hytype\fR (C): A purported
attribute\(hytype used as an argument of the abstract\(hyoperation is not
one of
those which is supported by the MS abstract\(hyservice\(hyprovider. If the MS
abstract\(hyservice\(hyprovider is able to carry out the operation anyway,
it is not prohibited from doing so.
.LP
c)
\fBInappropriate\(hymatching \fR (C): The filter contains a
filter\(hyitem in which an attribute is matched using an operation (equality,
ordering, or substrings) that is not defined for that attribute.
.LP
d)
\fBAttribute\(hytype\(hynot\(hysubscribed\fR (C): An attribute\(hytype
used as an argument of the abstract\(hyoperation is not one of those to
which the MS abstract\(hyservice\(hyuser has subscribed.
.LP
\fINote\fR \ \(em\ A change of the subscription is not
necessarily reflected in the attributes present in an entry created before
the change.
.LP
\fR
e)
\fBInappropriate\(hyfor\(hyoperation\fR (C): An attribute\(hytype used
as an argument of the abstract\(hyoperation is unsuitable for its required
use.
.sp 1P
.LP
9.3
\fIAuto\(hyaction\(hyrequest\(hyerror\fR
.sp 9p
.RT
.PP
An \fBauto\(hyaction\(hyrequest\(hyerror\fR reports a problem related to
registration of an auto\(hyaction.
.RT
.LP
AutoActionRequestError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problems\ [0]
SET SIZE (1\|.\|.\|ub\(hyauto\(hyregistrations) OF
SET\|{
.LP
\ \ \ \ problem
[0]\ Auto\(hyActionRequestProblem,
.LP
\ \ \ \ type
[1]\ AutoActionType\|}\|}
.LP
AutoActionRequestProblem ::= INTEGER\|{
.LP
unavailable\(hyauto\(hyaction\(hytype
(0),
.LP
auto\(hyaction\(hytype\(hynot\(hysubscribed
(1)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems\fR (M): The particular problems encountered. Any
numbers of individual problems may be indicated, each problem being accompanied
by an indication of the \fBauto\(hyaction\(hytype\fR which caused the problem:
.LP
\fR
a)
\fBUnavailable\(hyauto\(hyaction\(hytype\fR : An auto\(hyaction\(hytype
used as an argument of the abstract\(hyoperation is not one of those which is
supported by the MS abstract\(hyservice\(hyprovider.
.bp
.LP
b)
\fBAction\(hytype\(hynot\(hysubscribed\fR : An action\(hytype used as
an argument of the abstract\(hyoperation is not one of those to which the
MS
abstract\(hyservice\(hyuser has subscribed.
.sp 1P
.LP
9.4\fR \fIDelete\(hyerror\fR
.sp 9p
.RT
.PP
A \fBdelete\(hyerror\fR reports a problem in an attempt to delete one or
more entries from an information\(hybase.
.RT
.LP
DeleteError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problems\ [0]\ SET SIZE (1\|.\|.\|ub\(hymessages) OF SET\|{
.LP
\ \ \ \ problem
[0]\ DeleteProblem,
.LP
\ \ \ \ sequence\(hynumber
[1]\ SequenceNumber\|}\|}
.LP
DeleteProblem ::= INTEGER\|{
.LP
child\(hyentry\(hyspecified
(0),
.LP
delete\(hyrestriction\(hyproblem
(1)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems\fR (M): The particular problems encountered. Any
number of individual problems may be indicated, each problem being accompanied
by an indication of the sequence\(hynumber of the entry which caused the
problem:
.LP
\fR
a)
\fBChild\(hyentry\(hyspecified\fR : An attempt has been made to delete
a child\(hyentry.
.LP
b)
\fBDelete\(hyrestriction\(hyproblem\fR : An attempt has been made to
violate a restriction specified for the Delete abstract\(hyoperation
(see\ \(sc\ 8.5).
.sp 1P
.LP
9.5
\fIFetch\(hyrestriction\(hyerror\fR
.sp 9p
.RT
.PP
A \fBfetch\(hyrestriction\(hyerror\fR reports an attempt to violate a
restriction associated with the fetch abstract\(hy
operation.
.RT
.LP
FetchRestrictionError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problems\ [0]\ SET SIZE (1\|.\|.\|ub\(hydefault\(hyregistrations)
OF SET\|{
.LP
\ \ \ \ problem
[3]\ FetchRestrictionProblem,
.LP
\ \ \ \ restriction
CHOICE\|{
.LP
\ \ \ \ \ content\(hytype
[0]\ ContentType,
.LP
\ \ \ \ \ eit
[1]\ MS\(hyEITs,
.LP
\ \ \ \ \ content\(hylength
[2]\ ContentLength\|}\|}\|}
.LP
FetchRestrictionProblem ::= INTEGER\|{
.LP
content\(hytype\(hyproblem
(1),
.LP
eit\(hyproblem
(2),
.LP
content\(hylength\(hyproblem
(3)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems\fR (M): The particular problems encountered. Any
number of individual problems may be indicated, each problem being accompanied
by an indication of the offending content\(hytype, encoded\(hyinformation\(hytype
or
content\(hylength which caused the problem:
.LP
a)
\fBContent\(hytype\(hyproblem\fR (C): The content\(hytype of the
message being fetched is disallowed by the fetch\(hyrestrictions currently in
force.
.LP
b)
\fBEit\(hyproblem\fR (C): The encoded\(hyinformation\(hytypes
requested in the Fetch abstract\(hyoperation are disallowed by the
fetch\(hyrestrictions currently in force.
.LP
\fR
c)
\fBContent\(hylength\(hyproblem\fR (C): The content\(hylength of
the message being fetched is longer than that allowed by the fetch\(hyrestrictions
currently in force.
.sp 1P
.LP
9.6
\fIInvalid\(hyparameters\(hyerror\fR
.sp 9p
.RT
.PP
An \fBinvalid\(hyparameters\(hyerror\fR reports a semantic problem in the
set of parameters received. This error would be used, for example, to report
that an optional parameter was present in the wrong context, or to report
that a
value for one of the parameters is inappropriate.
.RT
.LP
InvalidParametersError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ NULL
.PP
This error has no parameters.
.bp
.sp 1P
.LP
9.7
\fIRange\(hyerror\fR
.sp 9p
.RT
.PP
A \fBrange\(hyerror\fR reports a problem related to the limit specified
in a selector as an argument to an abstract\(hyoperation.
.RT
.LP
RangeError ::= ABSTRACT\(hyERROR
.LP
PARAMETER SET\|{
.LP
\ \ problem
[0]\ RangeProblem\|}
.LP
RangeProblem ::= INTEGER\|{
.LP
reversed
(0)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems\fR (M): The particular problems encountered:
.LP
\fR
a)
\fBReversed\fR (C): The upper bound indicated a
sequence\(hynumber or creation\(hytime before that indicated by the lower
bound.
.sp 1P
.LP
9.8
\fISecurity\(hyerror\fR
.sp 9p
.RT
.PP
A \fBsecurity\(hyerror\fR reports that the requested abstract\(hyoperation
cannot be provided because it would violate the security\(hypolicy in force.
This error is defined in Recommendation\ X.411.
.RT
.sp 1P
.LP
9.9
\fISequence\(hynumber\(hyerror\fR
.sp 9p
.RT
.PP
A \fBSequenceNumberError\fR reports a problem related to the
sequence\(hynumber specified in an argument to an abstract\(hyoperation.
.RT
.LP
SequenceNumberError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problems\ [1]\ SET SIZE (1\|.\|.\|ub\(hymessages) OF SET\|{
.LP
\ \ \ \ problem
[0]\ SequenceNumberProblem,
.LP
\ \ \ \ sequence\(hynumber
[1]\ SequenceNumber\|}}
.LP
SequenceNumberProblem ::= INTEGER\|{
.LP
no\(hysuch\(hyentry
(0)\|}\ (0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblems\fR (M)\ :\ The particular problems encountered. Any
numbers of individual problems may be indicated, each problem being accompanied
by an indication of the sequence\(hynumbers which caused the problem:
.LP
a)
\fBNo\(hysuch\(hyentry\fR \ :\ The sequence\(hynumber supplied does
not match that of any entry in the information\(hybase.
.sp 1P
.LP
9.10
\fIService\(hyerror\fR
.sp 9p
.RT
.PP
A \fBservice\(hyerror\fR reports an error related to the provision of the
service.
.RT
.LP
ServiceError ::= ABSTRACT\(hyERROR
.LP
PARAMETER\ SET\|{
.LP
\ \ problem
[0]\ ServiceProblem\|}
.LP
ServiceProblem ::= INTEGER\|{
.LP
busy
(0),
.LP
unavailable
(1),
.LP
unwilling\(hyto\(hyperform
(2)\|}\|(0\|.\|.\|ub\(hyerror\(hyreasons)
.PP
The parameter has the following meaning:
.LP
1)
\fBProblem\fR (M): The particular problem encountered:
.LP
\fR
a)
\fBBusy\fR (C): The MS, or some part of it, is presently too busy to
perform the requested abstract\(hyoperation, but may be able to do so after
a short while.
.LP
b)
\fBUnavailable\fR (C): The MS, or some part of it, is
presently unavailable.
.LP
c)
\fBUnwilling\(hyto\(hyperform\fR (C): The MS is not prepared to execute
this request, because it would lead to excessive consumption of
resources.
.bp
.LP
SECTION\ 3\ \(em\
GENERAL\(hyATTRIBUTE\(hyTYPES\ AND\ GENERAL\(hyAUTO\(hyACTION\(hyTYPES
.sp 1P
.RT
.sp 2P
.LP
\fB10\fR \fBOverview\fR
.sp 1P
.RT
.PP
The MS information\(hymodel and the \fBattribute\fR and \fBauto\(hyaction\fR
concepts were introduced in\ \(sc\ 6.3.3 and\ \(sc\ 6.5. Paragraph\ 11
defines the
\fBgeneral\(hyattribute\(hytypes\fR which are specified for MS. Paragraph\
12 defines the \fBgeneral\(hyauto\(hyaction\(hytypes\fR which are specified
for MS.
.RT
.sp 2P
.LP
\fB11\fR \fBGeneral\(hyattribute\(hytypes\fR
.sp 1P
.RT
.PP
The \fBgeneral\(hyattribute\(hytypes\fR are valid for all message
content\(hytypes. Other attribute\(hytypes, which are content\(hyspecific,
are defined in their respective Recommendations, e.g. the IPMS\(hyspecific
attribute\(hytypes for MS are defined in Annex\ C of Recommendation\ X.420.
.RT
.sp 1P
.LP
11.1
\fIGeneral\(hyattribute\(hytypes overview\fR
.sp 9p
.RT
.PP
The \fBgeneral\(hyattributes\fR that may occur in a stored\(hymessages
information\(hybase entry are listed in Table\ 1/X.413. They are constructed
mainly from the parameter information from the MessageDelivery and ReportDelivery
abstract\(hyoperations of the MTS abstract\(hyservice as defined in\ \(sc\ 8 of
Recommendation\ X.411, and such attributes are correspondingly named. Some
\fBgeneral\(hyattributes\fR are generated, and some of these also maintained,
by the MS.
.PP
Table 1/X.413 defines the various \fBgeneral\(hyattributes\fR and defines
the following for each attribute\(hytype:
.RT
.LP
\(em
whether the attribute\(hytype is single\(hyvalued or multi\(hyvalued;
.LP
\(em
whether or not support by the MS and the accessing UA is
mandatory or optional;
.LP
\(em
whether the attribute\(hytype is always present, conditionally present,
or absent in a delivered\(hymessage entry, a delivered\(hyreport entry,
or a returned\(hycontent entry respectively;
.LP
\(em
whether or not the attribute\(hytype can be returned in a list or an
alert abstract\(hyoperation;
.LP
\(em
whether or not the attribute\(hytype may be used in a summarize abstract\(hyoperation.
.LP
\fINote\fR \ \(em\ Only for simple ASN.1 data\(hytypes.
.PP
\fR
For a more detailed description of the classification in
Table\ 1/X.413 refer to the conventions in\ \(sc\ 5.2.
.PP
An optional attribute\(hytype is only suported by an MS if the support
of that attribute\(hytype has successfully been subscribed to (which implies
that the MS and the accessing UA supports that attribute). Subscription
to optional
attribute\(hytypes can be per attribute\(hytype per UA.
.RT
.sp 1P
.LP
11.2
\fIDescription of the general\(hyattribute\(hytypes\fR
.sp 9p
.RT
.PP
The following paragraphs contain a short description of each
\fBgeneral\(hyattribute\(hytype\fR together with its abstract\(hysyntax
using the ATTRIBUTE macro described in\ \(sc\ 6.3.
.PP
It should be noted that some \fBgeneral\(hyattributes\fR are used primarily
for filtering and listing purposes while others can contain more complex
(further structured ASN.1 data\(hytypes) and potentially voluminous information.
Only a few \fBgeneral\(hyattributes\fR are suitable for summaries.
.RT
.sp 1P
.LP
11.2.1
\fIChild\(hysequence\(hynumbers\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, contains one or
more \*Upointers\*U to the next level of child\(hyentries, if such exist. It is
generated by the MS. It is present in a parent\(hyentry that has one or more
child\(hyentries associated with it. It is absent in an entry without
child\(hyentries.
.RT
.LP
ms\(hychild\(hysequence\(hynumbers ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX\(hySequenceNumber
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hychild\(hysequence\(hynumbers
.bp
.ce
\fBH.T. [T1.413]\fR
.ce
TABLE\ 1/X.413
.ce
\fBGeneral\(hyattribute\(hytypes for the stored\(hymessages\fR
.ps 9
.vs 11
.nr VS 11
.nr PS 9
.TS
center box;
cw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
Attribute\(hytype\(hyname Single/ multi valued T{
Support level by MS and access UA
T} T{
Presence in delivered message entry
T} T{
Presence in delivered report entry
T} T{
Presence in returned\(hy
content entry
T} Available for list, alert Available for summarize
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBChild\(hysequence\(hynumbers\fR
T} M M C C C Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBContent\fR S M P \(em P N N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBContent\(hyconfidentiality\(hyalgorithm\(hyidentifier\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBContent\(hycorrelator\fR
T} S O \(em C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBContent\(hyidentifier\fR
T} S O C C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBContent\(hyintegrity\(hycheck\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBContent\(hylength\fR S O P \(em P Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBContent\(hyreturned\fR S O \(em P \(em Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBContent\(hytype\fR S M P C C Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBConversion\(hywith\(hyloss\(hyprohibited\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBConverted\(hyEITs\fR M O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBCreation\(hytime\fR S M P P P Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBDelivered\(hyEITs\fR M O P \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBDelivery\(hyflags\fR S O P \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBDL\(hyexpansion\(hyhistory\fR
T} M O C C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBEntry\(hystatus\fR S M P P P Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBEntry\(hytype\fR S M P P P Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBIntended\(hyrecipient\(hyname\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hydelivery\(hyenvelope\fR
T} S M P \(em \(em N N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hydelivery\(hyidentifier\fR
T} S O P \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hydelivery\(hytime\fR
T} S O P \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hyorigin\(hyauthentification\(hycheck\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hysecurity\(hylabel\fR
T} S O C C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBMessage\(hysubmission\(hytime\fR
T} S O P \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBMessage\(hytoken\fR S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBOriginal\(hyEITs\fR M O C C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBOriginator\(hycertificate\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBOriginator\(hyname\fR S O P \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBOther\(hyrecipient\(hynames\fR
T} M O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBParent\(hysequence\(hynumber
T} S M C \(em P Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBPer\(hyrecipient\(hyreport\(hydelivery\(hyfields\fR
T} M M \(em P \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBPriority\fR S O P \(em \(em Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBProof\(hyof\(hydelivery\(hyrequest\fR
T} S O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBRedirection\(hyhistory\fR
T} M O C \(em \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBReport\(hydelivery\(hyenvelope\fR
T} S M \(em P \(em N N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBReporting\(hyDL\(hyname\fR
T} S O \(em C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBReporting\(hyMTA\(hycertificate\fR
T} S O \(em C \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBReport\(hyorigin\(hyauthentification\(hycheck\fR
T} S O C C \(em Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBSecurity\(hyclassification\fR
T} S O C C \(em Y Y
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
\fBSequence\(hynumber\fR S M P P P Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBSubject\(hysubmission\(hyidentifier\fR
T} S M \(em P \(em Y N
_
.T&
lw(84p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) | cw(24p) | cw(18p) .
T{
\fBThis\(hyrecipient\(hyname\fR
T} S O P \(em \(em Y N
_
.TE
.nr PS 9
.RT
.ad r
\fBTable 1/X.413 [T1.413], p.\fR
.sp 1P
.RT
.ad b
.RT
.LP
.bp
.sp 1P
.LP
11.2.2
\fIContent\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the complete content of a message as
delivered by the MessageDelivery abstract\(hyoperation or as returned\(hycontent
by the ReportDelivery abstract\(hyoperation. For more details see\ \(sc\(sc\
8.2.1.1.1.37 and\ 8.3.1.2.1.14 of Recommendation\ X.411.
.RT
.LP
ms\(hycontentATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX Content
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent
.sp 1P
.LP
11.2.3
\fIContent\(hyconfidentiality\(hyalgorithm\(hyidentifier\fR
.sp 9p
.RT
.PP
\fR
This general attribute contains the \fBalgorithm\(hyidentifier\fR used
by the originator of the message to encrypt the message content. It may
be
generated by the originator of the message. For further details see\ \(sc\
8.5.10 of Recommendation\ X.411.
.RT
.LP
mt\(hycontent\(hyconfidentiality\(hyalgorithm\(hyidentifier ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX AlgorithmIdentifier
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hyconfidentiality\(hyalgorithm\(hyidentifier
.sp 1P
.LP
11.2.4
\fIContent\(hycorrelator\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains information to enable correlation of
the content of the message. It may be generated by the originating UA.
For more details see\ \(sc\ 8.2.1.1.1.36 of Recommendation\ X.411.
.RT
.LP
mt\(hycontent\(hycorrelator ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ContentCorrelator
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hycorrelator
.sp 1P
.LP
11.2.5
\fIContent\(hyidentifier\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains an identifier for the content of
the message. It may be generated by the originating UA. For more details
see\ \(sc\ 8.2.1.1.1.35 of Recommendation\ X.411.
.RT
.LP
mt\(hycontent\(hyidentifier ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ContentIdentifier
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hyidentifier
.sp 1P
.LP
11.2.6
\fIContent\(hyintegrity\(hycheck\fR
.sp 9p
.RT
.PP
This general attribute provides the recipient(s) of the message
with a means of validating that the message content has not been modified.
It may be generated by the originator of the message and may specify a
different value for each recipient of the message. For further details
see\ \(sc\ 8.2.1.1.28 of Recommendation\ X.411.
.RT
.LP
mt\(hycontent\(hyintegrity\(hycheck ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ContentIntegrityCheck
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hyintegrity\(hycheck
.sp 1P
.LP
11.2.7
\fIContent\(hylength\fR
.sp 9p
.RT
.PP
This general\(hyattribute gives the length of the content in octets of
a message as delivered by the MessageDelivery abstract\(hyoperation or
of a
returned\(hycontent (if any) notified by the ReportDelivery abstract\(hy
operation.
Where there is no such returned\(hycontent, this attribute is absent. It is
generated by the MS.
.RT
.LP
ms\(hycontent ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ContentLength
.LP
MATCHES FOR ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hylength
.bp
.sp 1P
.LP
11.2.8
\fIContent\(hyreturned\fR
.sp 9p
.RT
.PP
This general\(hyattribute indicates whether a content has been
returned in the ReportDelivery abstract\(hyoperation. It is generated by the
MS.
.RT
.LP
ms\(hycontent\(hyreturned ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX BOOLEAN
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hyreturned
.sp 1P
.LP
11.2.9
\fIContent\(hytype\fR
.sp 9p
.RT
.PP
This general\(hyattribute is generated from the content\(hytype in the
MessageDelivery or ReportDelivery abstract\(hyoperation. See also\ \(sc\
8.2.1.1.1.34 of Recommendation\ X.411.
.RT
.LP
mt\(hycontent\(hytype ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX OBJECT IDENTIFIER
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycontent\(hytype
.sp 1P
.LP
11.2.10
\fIConversion\(hywith\(hyloss\(hyprohibited\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains information about whether
conversion with loss of information was allowed or prohibited. For further
details see\ \(sc\ 8.2.1.1.1.10 of Recommendation\ X.411.
.RT
.LP
mt\(hyconversion\(hywith\(hyloss\(hyprohibited ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ConversionWithLossProhibited
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyconversion\(hywith\(hyloss\(hyprohibited
.sp 1P
.LP
11.2.11
\fIConverted\(hyEITs\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, identifies the
encoded\(hyinformation\(hytypes of the content after conversion, as indicated
by
MessageDelivery or ReportDelivery abstract\(hyoperation. It is generated by the
MS. It is absent if no conversion took place. For more details
see\ \(sc\ 8.3.1.1.1.8 and\ 8.3.1.2.1.5 of Recommendation\ X.411.
.RT
.LP
ms\(hyconverted\(hyEITs ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MS\(hyEIT
.LP
MATCHES FOR EQUALITY
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hyconverted\(hyEITs
.sp 1P
.LP
11.2.12
\fICreation\(hytime\fR
.sp 9p
.RT
.PP
This general\(hyattribute gives the time when the entry was created in
the MS. It is generated by the MS. For more details see\ \(sc\ 6.3.2.
.PP
\fINote\fR \ \(em\ Two or more consecutive entries may have the same
creation\(hytime.
.RT
.LP
ms\(hycreation\(hytime ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX CreationTime
.LP
MATCHES FOR EQUALITY ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hycreation\(hytime
.sp 1P
.LP
11.2.13
\fIDelivered\(hyEITs\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, identifies the
encoded\(hyinformation\(hytypes in the content of the message as delivered.
It is
generated by the MS based on information about the original\(hyEITSs and the
converted\(hyEITs in the MessageDelivery abstract\(hyoperation.
.RT
.LP
ms\(hydelivered\(hyEITs ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MS\(hyEIT
.LP
MATCHES FOR EQUALITY
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hydelivered\(hyEITs
.bp
.sp 1P
.LP
11.2.14
\fIDelivery\(hyflags\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains information of the delivery.
Presently, it is only used for indicating implicit\(hyconversion of the
content. For more details see\ \(sc\ 8.2.1.1.1.9 of Recommendation\ X.411.
.RT
.LP
mt\(hydelivery\(hyflags ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX DeliveryFlags
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hydelivery\(hyflags
.sp 1P
.LP
11.2.15
\fIDL\(hyexpansion\(hyhistory\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, is used to show the
history of distribution\(hylist expansion. It contains one or more
distribution\(hylist names used during the expansion process. It is absent
if the delivery to this recipient did not involve any expansion of a
distribution\(hylist. For more details see\ \(sc\ 8.3.1.1.1.7 of
Recommendation\ X.411.
.RT
.LP
mt\(hydl\(hyexpansion\(hyhistory ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX DLExpansionHistory
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hydl\(hyexpansion\(hyhistory
.sp 1P
.LP
11.2.16
\fIEntry\(hystatus\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the current status of an entry in the
stored\(hymessages information\(hybase. It is created and maintained by
he MS.
For more details see\ \(sc\ 6.4.
.RT
.LP
ms\(hyentry\(hystatus ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX EntryStatus
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyentry\(hystatus
.sp 1P
.LP
11.2.17
\fIEntry\(hytype\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains information about whether an entry concerns
a delivered message or a delivered report. It is generated by the
MS.
.RT
.LP
ms\(hyentry\(hytype ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX EntryType
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyentry\(hytype
.LP
EntryType ::= INTEGER\|{
.LP
delivered\(hymessage
(0),
.LP
delivered\(hyreport
(1),
.LP
returned\(hycontent
(2)\ (0\|.\|.\|ub\(hyentry\(hytypes)\|}
.sp 1P
.LP
11.2.18
\fIIntended\(hyrecipient\(hyname\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the O/R\(hyname of the originally
intended recipient if the message has been redirected, with each value
representing one redirection. For more details see\ \(sc\ 8.3.1.1.1.4 of
Recommendation\ X.411.
.RT
.LP
mt\(hyintended\(hyrecipient\(hyname ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ORName
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyintended\(hyrecipient\(hyname
.bp
.sp 1P
.LP
11.2.19
\fIMessage\(hydelivery\(hyenvelope\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the complete
\fBmessage\(hydelivery\(hyenvelope\fR of a message as delivered by the
MessageDelivery
abstract\(hyoperation. For more details see\ \(sc\ 9 of Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hydelivery\(hyenvelope ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageDeliveryEnvelope
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hydelivery\(hyenvelope
.sp 1P
.LP
11.2.20
\fIMessage\(hydelivery\(hyidentifier\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the \fBmessage\(hydelivery\(hyidentifier\fR
from the MessageDelivery abstract\(hyoperation. For more details see\ \(sc\
8.3.1.1.1.1 of Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hydelivery\(hyidentifier ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageDeliveryIdentifier
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hydelivery\(hyidentifier
.sp 1P
.LP
11.2.21
\fIMessage\(hydelivery\(hytime\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the \fBmessage\(hydelivery\(hytime\fR from
the MessageDelivery abstract\(hyoperation. For more details see\ \(sc\
8.3.1.1.1.2 of Recommendation\ X.411.
.PP
\fINote\fR \ \(em\ There is no general\(hyattribute corresponding to the
delivery\(hytime parameter of the ReportDelivery abstract\(hyoperation,
because in
order to be useful, this delivery\(hytime must be correlated with the name
of the recipient the message was delivered to. This information is included
in the
report\(hyinformation general\(hyattribute.
.RT
.LP
mt\(hymessage\(hydelivery\(hytime ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageDeliveryTime
.LP
MATCHES FOR EQUALITY ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hydelivery\(hytime
.sp 1P
.LP
11.2.22
\fIMessage\(hyorigin\(hyauthentication\(hycheck\fR
.sp 9p
.RT
.PP
This general attribute is computed using the algorithm identified by the
message\(hyorigin\(hyauthentication\(hyidentifier. It provides the recipient(s)
of the message with a means of authenticating the origin of the message
and may be generated by the originator of the message. For further details
see\ \(sc\ 8.2.1.1.1.29 of Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hyorigin\(hyauthentication\(hycheck ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageOriginAuthenticationCheck
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hyorigin\(hyauthentication\(hycheck
.sp 1P
.LP
11.2.23
\fIMessage\(hysecurity\(hylabel\fR
.sp 9p
.RT
.PP
This general attribute comprises a set of security attributes which may
include a security\(hypolicy\(hyidentifier, a security\(hyclassification,
a
privacy\(hymark, and a set of security\(hycategories. For further details
see\ \(sc\ 8.2.1.1.1.30 of Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hysecurity\(hylabel ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageSecurityLabel
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hysecurity\(hylabel
.sp 1P
.LP
11.2.24
\fIMessage\(hysubmission\(hytime\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the \fBmessage\(hysubmission\(hytime\fR
from a MessageDelivery abstract\(hyoperation. For more details see\ \(sc\
8.2.1.1.2.2 of
Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hysubmission\(hytime ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageSubmissionTime
.LP
MATCHES FOR EQUALITY ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hysubmission\(hytime
.bp
.sp 1P
.LP
11.2.25
\fIMessage\(hytoken\fR
.sp 9p
.RT
.PP
This general attribute contains the token associated with the
message. It is generated by the originator of the message and may contain a
different value for each recipient of the message. For further details
see\ \(sc\ 8.2.1.1.1.26 of Recommendation\ X.411.
.RT
.LP
mt\(hymessage\(hytoken ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MessageToken
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hymessage\(hytoken
.sp 1P
.LP
11.2.26
\fIOriginal\(hyEITs\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, contains the
\fBorginal encoded\(hyinformation\(hytypes\fR from the MessageDelivery
abstract\(hyoperation. It is generated by the MS. For more details
see\ \(sc\ 8.2.1.1.1.33 of Recommendation\ X.411.
.RT
.LP
ms\(hyoriginal\(hyEITs ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX MS\(hyEIT
.LP
MATCHES FOR EQUALITY
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hyoriginal\(hyEITs
.sp 1P
.LP
11.2.27
\fIOriginator\(hycertificate\fR
.sp 9p
.RT
.PP
This general attribute, contains the certificate of the originator of the
message. It is generated by a trusted source (e.g.\ a
certification\(hyauthority), and may be supplied by the originator of the
message. For further details see\ \(sc\ 8.2.1.1.1.25 of Recommendation\
X.411.
.RT
.LP
mt\(hyoriginator\(hycertificate ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX OriginatorCertificate
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyoriginator\(hycertificate
.sp 1P
.LP
11.2.28
\fIOriginator\(hyname\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the O/R\(hyname of the originator from
the MessageDelivery abstract\(hyoperation. For more details see\ \(sc\
8.2.1.1.1.1 of Recommendation\ X.411.
.RT
.LP
mt\(hyoriginator\(hyname ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ORName
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyoriginator\(hyname
.sp 1P
.LP
11.2.29
\fIOther\(hyrecipient\(hynames\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, contains the
O/R\(hynames of all other specified recipients, if any, of the message from the
MessageDelivery abstract\(hyoperation. For more details see\ \(sc\ 8.3.1.1.1.6
of
Recommendation\ X.411.
.RT
.LP
mt\(hyother\(hyrecipient\(hynames ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ORName
.LP
MATCHES FOR EQUALITY
.LP
MUTLI VALUE
.LP
::= id\(hyatt\(hyother\(hyrecipient\(hynames
.sp 1P
.LP
11.2.30
\fIParent\(hysequence\(hynumber\fR
.sp 9p
.RT
.PP
This general\(hyattribute, points to a parent\(hyentry. It is generated
by the MS. It is always present in a child\(hyentry and is absent in a
main\(hyentry.
.RT
.LP
ms\(hyparent\(hysequence\(hynumber ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX SequenceNumber
.LP
MATCHES FOR EQUALITY ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyparent\(hysequence\(hynumber
.bp
.sp 1P
.LP
11.2.31
\fIPer\(hyrecipient\(hyreport\(hydelivery\(hyfields\fR
.sp 9p
.RT
.PP
This general\(hyattribute, which is multi\(hyvalued, contains report
information on a per\(hyrecipient basis from the ReportDelivery
abstract\(hyoperation. For more details see\ \(sc\ 8.3.1.2 of
Recommendation\ X.411.
.RT
.LP
mt\(hyper\(hyrecipient\(hyreport\(hydelivery\(hyfields ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX PerRecipientReportDeliveryFields
.LP
MUTLI VALUE
.LP
::= id\(hyatt\(hyper\(hyrecipient\(hyreport\(hydelivery\(hyfields
.sp 1P
.LP
11.2.32
\fIPriority\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the relative \fBpriority\fR of the
message from the MessageDelivery abstract\(hyoperation. If no value is
supplied in the MessageDelivery abstract\(hyoperation parameter, the MS
uses its default
value when generating this attribute. For more details see\ \(sc\ 8.2.1.1.1.8
of
Recommendation\ X.411.
.RT
.LP
mt\(hypriority ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX Priority
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hypriority
.sp 1P
.LP
11.2.33
\fIProof\(hyof\(hydelivery\(hyrequest\fR
.sp 9p
.RT
.PP
This general attribute indicates whether or not the originator of the message
requires \fBproof\(hyof\(hydelivery\fR of the message to the recipient.
It
may be generated by the originator of the message and may specify a different
value for each recipient of the message. For more details see\ \(sc\ 8.2.1.1.1.32
of Recommendation\ X.411.
.RT
.LP
mt\(hyproof\(hyof\(hydelivery\(hyrequest ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ProofOfDeliveryRequest
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyproof\(hyof\(hydelivery\(hyrequest
.sp 1P
.LP
11.2.34
\fIRedirection\(hyhistory\fR
.sp 9p
.RT
.PP
The general\(hyattribute, which is multi\(hyvalued, contains the
history of recipient redirection(s) with reasons(s) from the MessageDelivery
or ReportDelivery abstract\(hyoperation. For more details see\ \(sc\ 8.3.1.1.1.5
of
Recommendation\ X.411.
.RT
.LP
mt\(hyredirection\(hyhistory ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX RedirectionHistory
.LP
MULTI VALUE
.LP
::= id\(hyatt\(hyredirection\(hyhistory
.sp 1P
.LP
11.2.35
\fIReport\(hydelivery\(hyenvelope\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains all the parameters from the
ReportDelivery abstract\(hyoperation, except for the returned\(hycontent (if
present). For more details see\ \(sc\ 8.3.1.2 of Recommendation\ X.411.
.RT
.LP
mt\(hyreport\(hydelivery\(hyenvelope ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ReportDeliveryEnvelope
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyreport\(hydelivery\(hyenvelope
.sp 1P
.LP
11.2.36
\fIReporting\(hyDL\(hyname\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the O/R\(hyname of the
distribution\(hylist that forwarded the report to the owner of this
distribution\(hylist. For more details see\ \(sc\ 8.3.1.2.1.4
of Recommendation\ X.411.
.RT
.LP
mt\(hyreporting\(hyDL\(hyname ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ReportingDLName
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyreporting\(hyDL\(hyname
.bp
.sp 1P
.LP
11.2.37
\fIReporting\(hyMTA\(hycertificate\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the certificate of the MTA that
generated the report. For more details see\ \(sc\ 8.3.1.2.1.12 of
Recommendation\ X.411.
.RT
.LP
mt\(hyreporting\(hyMTA\(hycertificate\(hyATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ReportingMTACertificate
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyreporting\(hyMTA\(hycertificate
.sp 1P
.LP
11.2.38
\fIReport\(hyorigin\(hyauthentication\(hycheck\fR
.sp 9p
.RT
.PP
The general\(hyattribute provides a means of authenticating the origin
of the report. For more details see\ \(sc\ 8.3.1.2.1.13 of
Recommendation\ X.411.
.RT
.LP
mt\(hyreport\(hyorigin\(hyauthentication\(hycheck ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ReportOriginAuthenticationCheck
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hyreport\(hyorigin\(hyauthentication\(hycheck
.sp 1P
.LP
11.2.39
\fISecurity\(hyclassification\fR
.sp 9p
.RT
.PP
This general\(hyattribute comprises the security\(hyclassification
parameter from the message\(hysecurity\(hylabel. It is defined as a separate
attribute to allow its use in the Summarize abstract\(hyoperation. For more
details see\ \(sc\ 8.5.9 of Recommendation\ X.411.
.RT
.LP
mt\(hysecurity\(hyclassification ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX SecurityClassification
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hysecurity\(hyclassification
.sp 1P
.LP
11.2.40
\fISequence\(hynumber\fR
.sp 9p
.RT
.PP
This general\(hyattribute is used to identify the entry itself. It is allocated
by the MS when the entry is created. For more details
see\ \(sc\ 6.3.2.
.RT
.LP
ms\(hysequence\(hynumber ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX SequenceNumber
.LP
MATCHES FOR EQUALITY ORDERING
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hysequence\(hynumber
.sp 1P
.LP
11.2.41
\fISubject\(hysubmission\(hyidentifier\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the message\(hysubmission\(hyidentifier
or the probe\(hysubmission\(hyidentifier of the subject of the report.
For more
details see\ \(sc\ 8.3.1.2.1.1 of Recommendation\ X.411.
.RT
.LP
mt\(hysubject\(hysubmission\(hyidentifier ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX SubjectSubmissionIdentifier
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hysubject\(hysubmission\(hyidentifier
.sp 1P
.LP
11.2.42
\fIThis\(hyrecipient\(hyname\fR
.sp 9p
.RT
.PP
This general\(hyattribute contains the O/R\(hyname of this (MS) recipient
from the MessageDelivery abstract\(hyoperation. For more details see\ \(sc\
8.3.1.1.1.3 of Recommendation\ X.411.
.RT
.LP
mt\(hythis\(hyrecipient\(hyname ATTRIBUTE
.LP
WITH ATTRIBUTE\(hySYNTAX ORName
.LP
MATCHES FOR EQUALITY
.LP
SINGLE VALUE
.LP
::= id\(hyatt\(hythis\(hyrecipient\(hyname
.LP
.bp